Skip to content
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

pypiwin32 version 222 - Failed to be installed #1151

Closed
kfirilani opened this issue Jan 25, 2018 · 17 comments

Comments

@kfirilani
Copy link

commented Jan 25, 2018

New version of pypiwin32 (version 222) updated on 25-1-2018 cannot be installed.

Sometimes, package is being installed, however when trying to import "win32api" module, an exception occurred.

Does anyone have this problem?

@kfirilani kfirilani changed the title pywin32 version 222 - Failed to be installed pypiwin32 version 222 - Failed to be installed Jan 25, 2018

@ghost

This comment has been minimized.

Copy link

commented Jan 25, 2018

I can confirm this issue. @mhammond Did you verify that the wheels work correctly?

@ghost ghost assigned mhammond Jan 25, 2018

@ghost

This comment has been minimized.

Copy link

commented Jan 25, 2018

Note: the "pypiwin32" project has ended; it's now simply a shim package that requires "pywin32".

@ghost ghost added the bug label Jan 25, 2018

tardyp added a commit to tardyp/buildbot that referenced this issue Jan 25, 2018
@tardyp

This comment has been minimized.

Copy link

commented Jan 25, 2018

@mhammond would have been nice to add a little message in the long_description stating that the pypiwin32 package is obsolete

@topnotcher

This comment has been minimized.

Copy link

commented Jan 26, 2018

Sometimes, package is being installed, however when trying to import "win32api" module, an exception occurred.

This:

>>> import win32api
ImportError: DLL load failed: The specified module could not be found.

This is in a virtualenv. It is trying to load one of the DLLs in pywin32_system32.

I don't know if the pywi32_postinstall script is even running, but I have my doubts -- the DLLs are not present in sys.prefix. In any case, I don't expect it to work. As far as I can tell, it installs to system32 or sys.prefix if that fails. I don't think sys.prefix is sufficient in the virtual environment -- it points to the root of the venv, which is not in PATH and does not contain python.exe (i.e. it's not a DLL search path).

(Edit: Okay, I see the README.MD says to run the post install script, but pip plays it fast and loose and skipped reading the readme.)

pypiwin32 seemed to work around this in the .pth file:
pypiwin32.pth:

import os;os.environ["PATH"]+=(';'+os.path.join(sitedir,"pypiwin32_system32"))
tardyp added a commit to tardyp/buildbot that referenced this issue Jan 26, 2018
tardyp added a commit to tardyp/buildbot that referenced this issue Jan 26, 2018
@mhammond

This comment has been minimized.

Copy link
Owner

commented Jan 26, 2018

The post_install script needs to be run as mentioned in readme.md. I can't find support for automatically running it when building the wheel.

@mhammond mhammond removed their assignment Jan 26, 2018

@mhammond

This comment has been minimized.

Copy link
Owner

commented Jan 26, 2018

I can confirm this issue. @mhammond Did you verify that the wheels work correctly?

See README.md for the issues I had. Unassigning as I'm not working on this, but PRs obviously welcome.

ghost pushed a commit that referenced this issue Jan 26, 2018
Fix loader path
Closes gh-1151.
@ghost ghost referenced this issue Jan 26, 2018
@ghost

This comment has been minimized.

Copy link

commented Jan 26, 2018

I've opened gh-1153 for a possible fix.

@jabdoa2

This comment has been minimized.

Copy link

commented Jan 28, 2018

Any chance you could remove the broken version from pypi until this is fixed? This generates a lot a user complaints for us because on of our dependencies depends on pypiwin32 on windows

@hirenvadalia hirenvadalia referenced this issue Jan 29, 2018
4 of 9 tasks complete
@mhammond

This comment has been minimized.

Copy link
Owner

commented Jan 29, 2018

depends on pypiwin32 on windows

I believe I've changed the pypiwin32 project so that build 222 is hidden while build 220 is visible. I made no changes to "pywin32" on pypi. Did that help?

@tardyp

This comment has been minimized.

Copy link

commented Jan 29, 2018

Hi @mhammond , I reverted my workaround at buildbot/buildbot#3930

but the CI still finds version 222 of pypiwin32:
https://ci.appveyor.com/project/djmitche/buildbot/build/1.0.5848/job/aeki06t49p12r3in

If I go on the pypi page, I still see that 222 is the latest version https://pypi.python.org/pypi/pypiwin32

jabdoa2 added a commit to missionpinball/mpf that referenced this issue Jan 29, 2018
@meejah

This comment has been minimized.

Copy link

commented Jan 29, 2018

We are seeing this problem on Tahoe-LAFS windows builds on Travis -- pinning to pypiwin32==219 is the solution that works so far.

@csm10495

This comment has been minimized.

Copy link

commented Jan 30, 2018

I'm seeing this too. Version 222 should be taken down from pypi until this is resolved. Forcing pypiwin32==219 works around this for me now.

csm10495 added a commit to csm10495/PyNPipInst that referenced this issue Jan 30, 2018
@mhammond

This comment has been minimized.

Copy link
Owner

commented Jan 30, 2018

pypi seems strange - I set build 222 to hidden, but when I perform a search for simply "pypiwin32" it still shows that build. I'm not even sure how build 222 ended up in that project - I only updated the "pywin32" project.

I just went ahead and removed build 222 completely from the pypiwin32 project - both build 220 and 219 are unhidden - but it's not clear to me if there is also an issue with build 220 causing everyone to pin versions to build 219.

@meejah

This comment has been minimized.

Copy link

commented Jan 30, 2018

@tardyp

This comment has been minimized.

Copy link

commented Jan 30, 2018

works for me as well.
Note that appveyor picks version 219 for python 2.7 and 3.5, and 220 for 3.6.

220 only has wheels for 3.6:
https://pypi.python.org/pypi/pypiwin32/220

thanks

@weiwongfaye

This comment has been minimized.

Copy link

commented Feb 13, 2018

@mhammond , same for me. One of our test machine sometimes fetch 219, sometimes 222.
currently, we just pin the version to 219 directly.

@johan-bjareholt

This comment has been minimized.

Copy link

commented Jul 4, 2018

This issue is really wierd.
When doing "python -m pip install pywin32" I still sometimes get the 222 version, forcing it with "python -m pip install pywin32>=223" works fine.

EDIT: I was wrong, what was happening was that when I installed it from a package which had it as a requirement in "setup.py" and ran it with "python3 ./setup.py install" the package did not install properly. However, when uninstalling it and installing it again but with pip instead it worked fine.

redreamality added a commit to redreamality/Windows-10-Toast-Notifications that referenced this issue Feb 6, 2019
Update requirements.txt
Since pypiwin32 is deprecated
> Note: the "pypiwin32" project has ended; it's now simply a shim package that requires "pywin32".
see: mhammond/pywin32#1151
Further more it will conflict with the current installed `pywin32`
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.