[issue34011] Default preference not given to venv DLL's

Change by Steve Dower : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue34011] Default preference not given to venv DLL's

Change by miss-islington : -- pull_requests: +9686 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34011] Default preference not given to venv DLL's

Change by miss-islington : -- pull_requests: +9687 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34011] Default preference not given to venv DLL's

Change by Pablo Galindo Salgado : -- pull_requests: +9685 stage: resolved -> patch review ___ Python tracker ___ ___

[issue34011] Default preference not given to venv DLL's

Pablo Galindo Salgado added the comment: This buildbot is failing when raising when creating subprocess.CalledProcessError: https://buildbot.python.org/all/#/builders/40/builds/1135/steps/3/logs/stdio test_defaults (test.test_venv.BasicTest) ... ok test_executable (test.test_venv.BasicTest)

[issue34011] Default preference not given to venv DLL's

Steve Dower added the comment: I agree with this only applying to 3.8 - removing the copied files on earlier versions seems like an unnecessary risk to compatibility. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.6, Python 3.7

[issue34011] Default preference not given to venv DLL's

Steve Dower added the comment: New changeset f14c28f39766855420dd58d209da4ad847f3030e by Steve Dower in branch 'master': bpo-34011: Fixes missing venv files and other tests (GH-9458) https://github.com/python/cpython/commit/f14c28f39766855420dd58d209da4ad847f3030e --

[issue34011] Default preference not given to venv DLL's

Change by Steve Dower : -- pull_requests: +8872 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34011] Default preference not given to venv DLL's

Steve Dower added the comment: This change breaks a number of tests when run on a proper installation, since we still need to copy pythonXY.dll or else python.exe refuses to start. Since I'm fixing these tests today, I'll also fix this issue. -- assignee: -> steve.dower

[issue34011] Default preference not given to venv DLL's

Vinay Sajip added the comment: New changeset 94487d45707772723ef19e86700a40a12743baa1 by Vinay Sajip in branch 'master': bpo-34011: Update code copying DLLs and init.tcl into venvs. (GH-8253) https://github.com/python/cpython/commit/94487d45707772723ef19e86700a40a12743baa1 --

[issue34011] Default preference not given to venv DLL's

Change by Vinay Sajip : -- keywords: +patch pull_requests: +7785 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue34011] Default preference not given to venv DLL's

Vinay Sajip added the comment: Hmmm. I managed to find a machine to install Python3.3.0 on, and it appears that even with that copy suite removed, the tests still work. So possibly it's something that changed between 3.3.0 alpha and 3.3.0 final. I can try removing the copy code for 3.8 but

[issue34011] Default preference not given to venv DLL's

Vinay Sajip added the comment: The code that does the copy is the original PEP 405 implementation code (from 26 May 2012). I'm fairly sure that these files were copied over only because (at least prior to the Python 3.3 release in September 2012) they were needed to be in the venv for the

[issue34011] Default preference not given to venv DLL's

Change by Eryk Sun : -- versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34011] Default preference not given to venv DLL's

Eryk Sun added the comment: Offhand I don't know why it copies PYD and DLL files from the DLLs directory. It's part of the standard library. The virtual environment should only need to copy or symlink the binaries in the application directory, such as python.exe, pythonw.exe,

[issue34011] Default preference not given to venv DLL's

New submission from Jonathan : I don't know if this is a bug or an odd design decision or just something that hasn't been considered or maybe I'm missing something. On Windows and I create a venv with Python 3.6.3: > python -m venv venv This creates a subdirectory called /venv. Inside this,