-
Notifications
You must be signed in to change notification settings - Fork 814
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
Pywin32 - Release 226 breaks Virtualenv. #1439
Comments
Version 226 of pywin32 fails to install inside a virtual environment. See mhammond/pywin32#1439.
Pywin32 was release on Nov. 10 and introduced an issue when running virtualenv on windows, mhammond/pywin32#1439. This causes our ci system to fail when trying to run the windows jobs because tox is uses virtualenv underneath. This commit adds a pin via the constraints file to ensure that we are installing the older version which does not have this problem.
This is because of pypa/virtualenv#228 (and it break pipenv as a consequence, too). |
I'm having this issue, too. Going back to 225 is a workaround for now. |
Pywin32 was release on Nov. 10 and introduced an issue when running virtualenv on windows, mhammond/pywin32#1439. This causes our ci system to fail when trying to run the windows jobs because tox is uses virtualenv underneath. This commit adds a pin via the constraints file to ensure that we are installing the older version which does not have this problem.
It would be good to also add some tests for the virtual environment use case, so that a commit like this could be caught earlier. |
Indeed, I have this with virtualenv 16.1.0. |
Same problem with windows 10 and python 3.7 |
We can use pywin 226 need to stick to 225. See: mhammond/pywin32#1439
Same issue here on python 3.7.5 64 bit, windows 10, virtualenv 16.7.7. Is anyone able to elaborate on the workaround setting the pywin version to an earlier one (e.g. when |
@elembie and anyone else who is looking, you can specify that you don't want version 226 for pywin. I'm using pipenv so something like [packages]
pywin32 = {version = "!= 226", sys_platform = "== 'win32'"} or similar in your requirements.txt (something like If you're installing with pip I think you can just specify the version directly $ pip install 'pywin32!=226' # add --force-reinstall if necessary |
which breaks virtual env see mhammond/pywin32#1439
used on windows with 'winpy32==226' see mhammond/pywin32#1439
For all who struggle to get tox running again, as I did, here is my solution:
This will prevent the installation of |
used on windows with 'winpy32==226' see mhammond/pywin32#1439
used on windows with 'winpy32==226' see mhammond/pywin32#1439
used on windows with 'winpy32==226' see mhammond/pywin32#1439
Sorry for the inconvenience - this should be fixed in build 227 |
Thanks @mhammond ! |
@mhammond Thanks for the quick fix 😃 |
Note that issues in this repository are only for bugs or feature requests in the pywin32.
If you need support or help using this package, please follow these instructions - support or help requests will be closed without comment.
For all bugs, please provide the following information.
Pip installation of packages in virtual environments after having installed Pywin32 should work.
I'm not exactly sure what is happening but it seems like Pywin32 - Release 226 overrides the
site.py
module to a degree: https://github.com/colour-science/colour/runs/296273919#step:6:71Pretty much same build with Release 225 was fine yesterday: https://github.com/colour-science/colour/commit/b8399d28760179f46f7090dd69457565d1754403/checks?check_suite_id=303070722#step:6:42
Python 2.7 and Pywin32 - Release 226
Cheers,
Thomas
The text was updated successfully, but these errors were encountered: