New submission from Christoph Reiter <[email protected]>:
I'm sure this is already filed somewhere, but I couldn't find anything.
Currently when installing packages with pip using a 64bit Python to --user and
then starting a 32bit Python things fail because they look up packages from the
same location:
.\python.exe -m site --user-base
C:\Users\user\AppData\Roaming\Python
For example trying to import numpy from a 32bit Python when it was installed
with 64bit:
>>> import numpy
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File
"C:\Users\user\AppData\Roaming\Python\Python39\site-packages\numpy\__init__.py",
line 143, in <module>
from . import _distributor_init
File
"C:\Users\user\AppData\Roaming\Python\Python39\site-packages\numpy\_distributor_init.py",
line 26, in <module>
WinDLL(os.path.abspath(filename))
File "C:\Python39-32\lib\ctypes\__init__.py", line 374, in __init__
self._handle = _dlopen(self._name, mode)
OSError: [WinError 193] %1 is not a valid Win32 application
I guess this isn't a very common problem, but in MSYS2 we are facing this issue
because users can easily switch between 32bit/64bit Python. We could patch
things, but I'm wondering if there are any plans to fix this in CPython itself
so we don't invent our own thing.
thanks
----------
components: Windows
messages: 386804
nosy: lazka, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Same userbase for 32bit and 64bit install on Windows causing conflicts
versions: Python 3.9
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue43195>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
