Message315424
PEP 405 says that the pyvenv.cfg file is found as follows:
« a pyvenv.cfg file is found either adjacent to the Python executable or one directory above it (if the executable is a symlink, it is not dereferenced), »
But in cpython if the executable is a symlink, it _is_ dereferenced before searching for pyvenv.cfg .
I've checked this behaviour with Python 3.5, 3.6, and today's 3.7 tip.
Looking in 3.7's getpath.c, calculate_path_impl() calls, in order:
calculate_program_full_path()
calculate_argv0_path()
calculate_read_pyenv()
It looks like the symlink resolution happens near the end of calculate_argv0_path().
I think this means that the 'home=' line in pyvenv.cfg files generated by the 'venv' module is irrelevant (and seems likely to confuse anyone who might try to construct a Python environment by imitating a built venv). |
|
Date |
User |
Action |
Args |
2018-04-17 21:48:28 | mattheww | set | recipients:
+ mattheww |
2018-04-17 21:48:27 | mattheww | set | messageid: <1524001707.98.0.682650639539.issue33302@psf.upfronthosting.co.za> |
2018-04-17 21:48:27 | mattheww | link | issue33302 messages |
2018-04-17 21:48:27 | mattheww | create | |
|