Steve Dower <steve.do...@python.org> 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 likely because it was run in the Visual Studio Developer Console, which overrides pip's platform detection making it think that it's a 32-bit runtime. The fix is slowly making its way through the various third-party projects that needed to be fixed, so soon the answer will be "python -m pip install --upgrade pip". Until then, you can either run Python using a regular command prompt/PowerShell prompt, or you can use Visual Studio's x64 command prompt instead. ---------- status: pending -> open _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44147> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
