Message388840
When using `python -m venv --upgrade someenv`, it rewrites `pyvenv.cfg` with the current python version but leaves the python symlinks untouched (https://github.com/python/cpython/blob/a8ef4572a6b28bcfc0b10b34fa4204954b9dd761/Lib/venv/__init__.py#L248)
This is of course fine when the original location of the Python interpreter is something like `/usr/bin/python3.9`, but when using pyenv it's a path containing the full version such as `/home/USER/.pyenv/versions/3.9.2/bin/python`, which makes in-place updates of minor Python versions harder than needed (manual update of the symlink needed).
IfF you agree that this change makes sense, I wouldn't mind sending a PR for this... |
|
Date |
User |
Action |
Args |
2021-03-16 13:57:10 | ThiefMaster | set | recipients:
+ ThiefMaster |
2021-03-16 13:57:10 | ThiefMaster | set | messageid: <1615903030.34.0.439862030712.issue43513@roundup.psfhosted.org> |
2021-03-16 13:57:10 | ThiefMaster | link | issue43513 messages |
2021-03-16 13:57:10 | ThiefMaster | create | |
|