Closed hoodmane closed 2 months ago
If this is happening it is a bug inside the python interpreter. Virtualenv looks up The python interpreters paths to determine where the purelib and platlib should be. Usually the platform library is the one containing the 64. If you check platforms like Fedora they handle this correctly. And that folder gets created accordingly.
If this is happening it is a bug inside the python interpreter.
Indeed on 64 bit ubuntu linux, venv creates a lib64 directory but virtualenv does not. On 64 bit fedora linux, both create lib64 directories.
Sounds to me like a buggy build of the Debian python.
The standard library venv module contains the following logic:
https://github.com/python/cpython/blob/14e1506a6d7056c38fbbc0797268dcf783f91243/Lib/venv/__init__.py?plain=1#L184-L189
The issue it refers to is https://github.com/python/cpython/issues/65396.
As far as I can tell,
virtualenv
does not ever make alib64
directory. I am curious what people think about whether or not similar logic should be included intovirtualenv
. This came up here: https://github.com/pypa/cibuildwheel/issues/1853cc @henryiii @QuLogic