-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pythonw.exe work in the same way as Python.exe #1686
Comments
Just notices the same behavior with the virtualenv 20.0.7. While I started pyw using subprocess.Popen(), if create virtualenv, activate it and directly run pythonw - its output will be visible in the same cmd window, if run pyw - new windows will be opened. P.S. Windows 10, Python 3.8.2 (64 bit), virtualenv 20.0.7 |
@AndrewUshakov your last comment is #1570 |
Thx! |
Hello, a fix for this issue has been released via virtualenv 20.0.9; see https://pypi.org/project/virtualenv/20.0.9/ (https://virtualenv.pypa.io/en/latest/changelog.html#v20-0-9-2020-03-08). Please give a try and report back if your issue has not been addressed; if not, please comment here, and we'll reopen the ticket. We want to apologize for the inconvenience this has caused you and say thanks for having patience while we resolve the unexpected bugs with this new major release. |
@gaborbernat: :) At first glance, everything is OK. Thank you!!! |
Pythonw.exe displays terminal in the same way as Python.exe, the terminal should not be displayed with this executable.
The text was updated successfully, but these errors were encountered: