[issue44147] [WinError 193] %1 is not a valid Win32 application

Erlend E. Aasland added the comment: Closing as not-a-bug. Feel free to reopen if we've missed anything. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue44147] [WinError 193] %1 is not a valid Win32 application

Erlend E. Aasland added the comment: Eryk, Steve, can we close this? AFAICT, this belongs to a user forum. Shreyan: it seems like a bpo bug to me. I have a feeling closing the issue will help. -- ___ Python tracker

[issue44147] [WinError 193] %1 is not a valid Win32 application

Shreyan Avigyan added the comment: Are you kidding me, What's going wrong with this issue tracker? I sent a message and it's set to open now? I'm not even a core dev or triager. What the heck is going on? -- ___ Python tracker

[issue44147] [WinError 193] %1 is not a valid Win32 application

Shreyan Avigyan added the comment: I've noticed whenever a core dev or triager sends a message the status is automatically set to open. But that's a different glitch or issue. -- status: pending -> open ___ Python tracker

[issue44147] [WinError 193] %1 is not a valid Win32 application

Erlend E. Aasland added the comment: Setting status to pending again. (Seems like bpo likes this dance) -- nosy: +erlendaasland status: open -> pending ___ Python tracker ___

[issue44147] [WinError 193] %1 is not a valid Win32 application

Eryk Sun added the comment: > There are a few ways to get multiple Python installs that > could lead to launching the wrong one through PATH. > --user is one of the least likely. As far as I was aware, a --user installation prior to Python 3.10 would be the common way to have the wrong

[issue44147] [WinError 193] %1 is not a valid Win32 application

Steve Dower added the comment: I didn't mean to change it. Maybe bpo did it automatically? There are a few ways to get multiple Python installs that could lead to launching the wrong one through PATH. --user is one of the least likely. -- status: open -> pending

[issue44147] [WinError 193] %1 is not a valid Win32 application

Eryk Sun added the comment: > For this issue, the PATH conflict would be that "pip" and "python" > refer to different Python installs. I'm aware of the problem for a per-user installation prior to 3.10. However, none of the install commands use the "--user" option, else I would have

[issue44147] [WinError 193] %1 is not a valid Win32 application

Steve Dower added the comment: >> Usually this error occurs due to PATH conflicts. > > Python 3.8 and above does not use PATH when importing extension modules For this issue, the PATH conflict would be that "pip" and "python" refer to different Python installs. However, this one is more

[issue44147] [WinError 193] %1 is not a valid Win32 application

Eryk Sun added the comment: The issue tracker is not a general support forum for software development. Please ask first on python-list or the users group on discuss.python.org. For now, I'm changing the status of this issue to pending. If the discussion determines that there's a bug in

[issue44147] [WinError 193] %1 is not a valid Win32 application

Shreyan Avigyan added the comment: Can you provide the full traceback log of at least one of the import failures. Try importing matplotlib, for example, and extract the traceback log. Usually this error occurs due to PATH conflicts. This issue is thoroughly discussed in

[issue44147] [WinError 193] %1 is not a valid Win32 application

New submission from Bassel : I'm trying to import these libraries in python using this code: import matplotlib as plt from matplotlib import style import pandas as pd import pandas_datareader.data as web I get unresolved import for each line. I installed them using the terminal of Visual