[issue43749] venv module does not copy the correct python exe

Eryk Sun added the comment: The code to copy a file could be rewritten to use a regex match. For example: # Copy src to dst. If src is a base executable, copy a launcher. dirname, filename = os.path.split(src) m =

[issue43749] venv module does not copy the correct python exe

Steve Dower added the comment: We'd also need to update the launcher to launch the executable with its name, which it currently doesn't do. I was looking at this recently for some other reason. -- ___ Python tracker

[issue43749] venv module does not copy the correct python exe

Change by Eryk Sun : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware versions: +Python 3.11 -Python 3.8 ___ Python tracker ___

[issue43749] venv module does not copy the correct python exe

Eryk Sun added the comment: The Windows implementation of symlink_or_copy() actually copies "python.exe" and "pythonw.exe" launchers from "Lib/venv/scripts/nt". One cannot simply copy the "python3.exe" executable because the required DLLs aren't copied. If this seemed to work when testing,

[issue43749] venv module does not copy the correct python exe

Vinay Sajip added the comment: New changeset bad16f0cf71a6b11ef62f86be6b3d3567cd70a16 by Miss Islington (bot) in branch '3.9': [3.9] bpo-43749: Ensure current exe is copied when using venv on windows (GH-25216) (GH-30033)

[issue43749] venv module does not copy the correct python exe

Vinay Sajip added the comment: New changeset bb8d645f3a09645686cf8f66bd46dcfa4efac713 by Miss Islington (bot) in branch '3.10': [3.10] bpo-43749: Ensure current exe is copied when using venv on windows (GH-25216) (GH-30034)

[issue43749] venv module does not copy the correct python exe

Mitchell Hentges added the comment: That's great, thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43749] venv module does not copy the correct python exe

Vinay Sajip added the comment: *3.8, I meant. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43749] venv module does not copy the correct python exe

Vinay Sajip added the comment: 3.10 and 3.9 - OK, but 3. is security fixes only, I'm afraid. -- ___ Python tracker ___ ___

[issue43749] venv module does not copy the correct python exe

Change by miss-islington : -- pull_requests: +28259 pull_request: https://github.com/python/cpython/pull/30034 ___ Python tracker ___

[issue43749] venv module does not copy the correct python exe

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +28258 pull_request: https://github.com/python/cpython/pull/30033 ___ Python tracker

[issue43749] venv module does not copy the correct python exe

Mitchell Hentges added the comment: Hey, can I request a backport of this change? For my use case, 3.9+ would be great, but going back to 3.7 should be viable? I trust your judgement :) I'll happily create the PRs for the backport, but it looks like the bug has to be indicated as "needs

[issue43749] venv module does not copy the correct python exe

Change by Vinay Sajip : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue43749] venv module does not copy the correct python exe

Niklas Rosenstein added the comment: To complete my previous comment, patching the function to see the command that is invoked, you can see it tries to invoke 'python3.exe' (seemingly derived from sys.executable) in the venv but the venv only contains 'python.exe'.

[issue43749] venv module does not copy the correct python exe

Niklas Rosenstein added the comment: I just encountered the same behavior. Steps to reproduce: * Install Python 3 (I used 3.9.5) on Windows * Use the Admin console to create a python3.exe link, e.g. cd "c:/Users/niklas/AppData/Local/Programs/Python/Python39" mklink python3.exe

[issue43749] venv module does not copy the correct python exe

Change by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43749] venv module does not copy the correct python exe

Change by Ian Norton : -- keywords: +patch pull_requests: +23954 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25216 ___ Python tracker ___

[issue43749] venv module does not copy the correct python exe

Ian Norton added the comment: This may also cause https://bugs.python.org/issue35644 -- ___ Python tracker ___ ___

[issue43749] venv module does not copy the correct python exe

New submission from Ian Norton : On windows, the venv module does not copy the correct python exe if the current running exe (eg sys.executable) has been renamed (eg, named python3.exe) venv will only make copies of python.exe, pythonw.exe, python_d.exe or pythonw_d.exe. If for example the