➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients ronaldoussoren
Date 2022-03-01.16:25:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1646151946.28.0.599042990928.issue46890@roundup.psfhosted.org>
In-reply-to
Content 
In python3.10 and earlier "python3 -m venv something" creates "something/bin/python" as a symlink to the interpreter itself.

In python3.11 (a5) the same command no longer creates "something/bin/python", but only the ".../python3" symlink. 

With this change the "python" command no longer refers to the interpreter in an activated virtualenv, but to a different binary on $PATH (if any).

I tested using the Python 3.11a5 installer for macOS on python.org.
History
Date User Action Args
2022-03-01 16:25:46ronaldoussorensetrecipients: + ronaldoussoren
2022-03-01 16:25:46ronaldoussorensetmessageid: <1646151946.28.0.599042990928.issue46890@roundup.psfhosted.org>
2022-03-01 16:25:46ronaldoussorenlinkissue46890 messages
2022-03-01 16:25:46ronaldoussorencreate