You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find poetry, pipenv use the virtualenv as the low level tool to create virutal env, and when work with pywin32, the install command will copy pywintypes39.dll into wrong directory, which cause the windows service installed by pywin32 cannot run.
I actually create the bug in poetry place, python-poetry/poetry#8612 (that thread use python 3.12.0, this thread use 3.9.11)
Maybe it is not virtualenv's bug either, and I didn't find clue with existing reported issues from here.
So, for the virtualenv created .venv folder and files structure, why put python.exe into the .venv/Scripts/? does it follow some PEP? why there are pyenv paths in the sys.path from the create .venv ? I see the "copy" argument is true by default, so why not just copy all files from pyenv installed python version?
Issue
I find poetry, pipenv use the virtualenv as the low level tool to create virutal env, and when work with pywin32, the
install
command will copypywintypes39.dll
into wrong directory, which cause the windows service installed by pywin32 cannot run.I actually create the bug in poetry place, python-poetry/poetry#8612 (that thread use python 3.12.0, this thread use 3.9.11)
Maybe it is not virtualenv's bug either, and I didn't find clue with existing reported issues from here.
So, for the virtualenv created .venv folder and files structure, why put
python.exe
into the.venv/Scripts/
? does it follow some PEP? why there are pyenv paths in thesys.path
from the create .venv ? I see the "copy" argument is true by default, so why not just copy all files from pyenv installed python version?I also use the virtualenv cli to create the .env, the result is same of poetry install.
Environment
windows 10 22H2
python for windows 3.10.11
pyenv-win 3.1.1
virtualenv 20.24.6
Output of the virtual environment creation
Make sure to run the creation with
-vvv --with-traceback
:The text was updated successfully, but these errors were encountered: