[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Matthew added the comment: > Probably there was also shadowing involved, since the built-in module doesn't > try to load anything else. Would be nice to know for sure (@Matthew) to make > sure we don't have some other issue here, but you're right, I don't see any > way for this to happen

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Steve Dower added the comment: > There is something fundamentally wrong with the way modules built into the > interpreter DLL (python3x.dll) are loaded if anything in sys.path or the > system PATH can cause an import to fail. Probably there was also shadowing involved, since the built-in

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Eryk Sun added the comment: There is something fundamentally wrong with the way modules built into the interpreter DLL (python3x.dll) are loaded if anything in sys.path or the system PATH can cause an import to fail. -- ___ Python tracker

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Matthew added the comment: Hello, Thanks for all the help people have given me! I've found the solution to my problem. The Environment Variable was set below every other, leading to a different Python interpreter to being used, which was probably bundled with a different software. I moved

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Steve Dower added the comment: It could also be something on your PATH interfering, as that particular ImportError could be pretty deep in the load chain. If none of the built-in options narrow it down enough, try https://pypi.org/project/dlltracer/ as well. Its output takes a bit of

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Jeremy Kloth added the comment: Well, to really see where things are going wrong, there is always the verbose option when launching Python: py -v -c "import binascii" This will output a lot of information but should help pin down what is exactly being imported when the error occurs. If

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Eryk Sun added the comment: The user site packages directory is architecture specific starting with 3.10, e.g. "%AppData%\Python\Python310-32\site-packages". The PYTHONPATH environment variable is shared by all versions. However, I don't understand how the binascii module could be a

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Change by Eric V. Smith : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

Jeremy Kloth added the comment: This error will occur when there is a 64-bit/32-bit conflict. Normally, Python extension modules are installed in architecture dependent locations, however user-installed modules (pip install) can share a path referred to as "user site". A quick check from

[issue47203] ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application.

New submission from StaticBits : When I try importing the default library "binascii" using the command "import binascii", the result is the following error (also in the title): ImportError: DLL load failed while importing binascii: %1 is not a valid Win32 application. I've reinstalled