[New-bugs-announce] [issue35450] venv module doesn't create a copy of python binary by default

[Marcin]

New submission from Marcin <marcin2006 at gmail.com>:

Hello,
from documentation:
https://docs.python.org/3/library/venv.html

"python3 -m venv /path/to/new/virtual/environment

Running this command creates the target directory (creating any parent directories that don’t exist already) and places a pyvenv.cfg file in it with a home key pointing to the Python installation from which the command was run. It also creates a bin (or Scripts on Windows) subdirectory containing **a copy** of the python binary (or binaries, in the case of Windows)."

This is not true. In my case it creates symlinks to python binary by default. This is quite different. Upgrading system's python version broke my virtual environment because I believed I'm having a static copy of python binary in my virtual environment.

----------
assignee: docs at python
components: Documentation
messages: 331445
nosy: docs at python, mkkot
priority: normal
severity: normal
status: open
title: venv module doesn't create a copy of python binary by default
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35450>
_______________________________________