[issue32444] python -m venv symlink dependency on how python binary is called is not documented

[Ned Deily]

Ned Deily  added the comment:

The behavior of venv has been changed in Python 3.9 to always create a 
"pythonM.N" link in the venv bin directory, in addition to "pythonM", 
regardless of how venv was invoked.

--
nosy: +ned.deily
resolution:  -> duplicate
stage: needs patch -> resolved
status: open -> closed
superseder:  -> shebanged scripts can escape from `venv` depending on how it 
was created
versions: +Python 3.9 -Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32444] python -m venv symlink dependency on how python binary is called is not documented

[R. David Murray]

R. David Murray  added the comment:

Actually, I'm going to reopen this as a doc issue because this behavior is not 
discussed by the docs that I can see, and it is important to know about when 
creating a venv.

--
assignee:  -> docs@python
components: +Documentation -Library (Lib)
nosy: +docs@python
resolution: not a bug -> 
stage: resolved -> needs patch
status: closed -> open
title: python -m venv has incongruous behavor creating binaries -> python -m 
venv symlink dependency on how python binary is called is not documented

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com