-
Notifications
You must be signed in to change notification settings - Fork 317
PyWin32 Post install Error: Missing pywin32_system32 folder in Lib/site-packages #58
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
Comments
hum, You may check that you see in your directory You can compare what you have with the unzipped directories that you have there (in (most common mistake, in my case, is to download the wrong version of wheel, a python3.3 or a 64bit one, or to download two different versions, and the wrong one is picked) |
I did have I downloaded I replaced pip, setuptools, and pywin32 wheels with yours just to be safe, but either way I received an error when pip was installed (so it seems to be a pip (un)install issue, not pywin32). Note: I am building winpython for Python 3.4.3 (32-bit).
Full verbose output:
|
I can confirm the file exists and the destination folder exists. My guess is perhaps some sort of string length limit for paths somewhere? I will try to move everything to a root somewhere (like the |
In the past, the |
As I try to avoid this historic bug to hit me from the start, by building in 'D:\winpython' it may have surfaced back undetected by me. Also, to Build myself, I open under a winpython3.4 64bit spyder environnement the Also, in that case, I parametrize Spyder to launch the execution in a |
If all the previous indication fails to make you succeed, I start to be out of ideas and may propose broader problems like:
|
Of course, I hope you are not on Windows XP |
XP, psshhh! Moved base winpython directory to flash drive which addressed three possibilities:
Successfully installed pywin32, build process is ongoing now, yeah! After I verify completely successful build, I will investigate which of the above 3 above possibilities caused the issue in the first place and let you know. Thanks for the help! |
You're welcome. |
Now I fell over the same issue as you... scratching my head
Now Inquiring forward, looking why 'pip.exe' is not created |
when Python3.4 installer runs
In the case of As Today, apparently, trying to do the same thing creates issues. ==> I don't understand clearly why, why not feb 28th on my PC , and why it would work for you now. Solution I found at the moment :
make.py patching (around line 480)
wppm.py patching (around line 385):
|
pushed to https://github.com/stonebig/winpython |
I think i found the root issue: a problem in WPPM + wheel. |
Solved on my pc, WPPM was relying on pip to install wheels, but not for their removal. |
last commit of #65 seems to solve this random issue (one day there, one day not). |
Using the latest commit (5b70c41), I am trying to build a custom winpython installation using Python 3.4.2 32-bit (Windows 7). I received an error that the pywin32_system32 folder does not exist in Lib/site-packages.
At what point should the pywin32_system32 folder be created in Lib/site-packages? I feel like simply checking if the folder exists and creating it if missing is not the correct solution...
The pywin32 wheel was downloaded from Christoph Gohlke's site.
Full output:
The text was updated successfully, but these errors were encountered: