-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Error Loading Python DLL when using 2.1.1dev-32bbb95 and --onefile for Windows .exe #1291
Comments
This might be my fault. Error code 14001 is "side-by-side configuration is incorrect". Could you do the following to get info about what the side-by-side loader is doing?
|
Also, could you run pyinstaller with the |
I had the same problem, I solved it by going back to the 67610f2 revision. |
I checked out the tip of the develop branch, I created the binary the same way. The output doesn't give us much: |
@psi29a Do you have any code example to reproduce this issue? |
Certainly: https://github.com/Mindwerks/worldengine :D |
Any shorter piece of code? |
Can you provide the Side-By-Side error information as described here? |
Python version? Side-By-Side error information? |
Try again with the latest |
GDAL was only recently added (in master/trunk, not yet tagged and released), my problem with pyinstaller on windows was months before this (in our 0.18 release). However, thank you for letting me know I have an additional concern. :P |
I'm having the same issue using 2.1.1.dev0 checked out today. I followed the instructions above to get the trace.txt and get:
|
@jonnojohnson PyInstaller 2.1 is far outdated. Please try the current |
@htgoebel I have tried using the Python3 branch but it won't build at all. I get a max recursion depth exceeded issue there. |
Just re-tried with today's python3 dev branch after the max recursion depth issue was fixed but I'm still getting this error.
|
Could you try building with |
Running the .exe after building with -F --clean I get:
|
I got something similar when trying to use py2exe last year. |
For the record, Anaconda includes pkg_resources as part of the setuptools egg:
Whereas regular Python includes it as a plain package inside
So it might be related to the way PyInstaller includes eggs? I'm not sure at this point. |
Hi all, I got the same problem with win 7 and python 2.7.10, but with pyinstaller 3.0. I don't have Anaconda and build in a directory (not onefile). Used to work with the development version I got, which was a couple of months old.
|
Could you try again with |
The --clean option seems to have resolved the issue. |
All right, I think I see what's happening now. The bincache stores cached versions of files that are modified while being collected, and if our modifications change, it will still use the cached version that has the old modifications. I think the solution is to add a "version" key to the cache.dat file in the bincache folder, and compare that with a version constant that gets updated whenever the modifications (the ones done in In this case, it's because manifests are modified differently in the version you previously had, versus version 3.0. |
|
@codewarrior0 could this be closed? |
Sure. I opened a new issue for the bincache thing. |
Thanks a lot your idea helped me a lot 👍 :-) |
This is exactly what I was looking for! I regularly create a 32-bit and a 64-bit version of my .exes and could not figure out why occasionally both would work without issue and at other times I'd be hit with the
|
I get the same problem, but PyInstaller Bootloader 3.x Error loading Python DLL: C:\Users\admin\AppData\Local\Temp_MEI12362\python35.d |
I'm not sure if perhaps something has changed with the --onefile option, but I recently cloned the latest report (2.1.1dev-32bbb95) and realized that all .exe's created reported:
Error loading Python DLL: C:\Users\USER\AppData\Local\Temp_MEI16922\python2
7.dll (error code 14001)
I used a previous version of pyinstaller (2.1.1dev-67610f2) and am no longer seeing the error. Nothing else was changed.
The text was updated successfully, but these errors were encountered: