Package: python3.5-venv Version: 3.5.2-5 Severity: important I had created and virtual python environment with pyvenv-3.4 in squeeze. Now after upgrading my debian system to stretch I wanted to upgrade this environment to the new python version with the following command:
pyvenv-3.5 --upgrade ~/python-envs/env/ In principle it worked, but in the bin/ directory of the env the symlinks to the python executable were not updated. ls -l ~/python-envs/env/bin/python* showed: lrwxrwxrwx 1 martin martin 48 Jun 7 07:48 /home/martin/python-envs/env/bin/ python -> /home/martin/python-envs/env/bin/python3.4 lrwxrwxrwx 1 martin martin 48 Jun 7 07:48 /home/martin/python-envs/env/bin/ python3 -> /home/martin/python-envs/env/bin/python3.4 lrwxrwxrwx 1 martin martin 18 Jun 7 07:48 /home/martin/python-envs/env/bin/ python3.4 -> /usr/bin/python3.4 lrwxrwxrwx 1 martin martin 18 Sep 28 11:47 /home/martin/python-envs/env/bin/ python3.5 -> /usr/bin/python3.5 So a symlink called "python3.5" linking to /usr/bin/python3.5 ist created, but the symlinks "python" and "python3", which should point to this new python3.5 are still linking to python3.4. Since /usr/bin/python3.4 is not there any more these symlinks are dead, so the environment is not working as it should. I updated the symlinks manually to get it to work again, but this bug should be fixed. Probably this bug has to be fixed upstream as well. -- DI Martin Perz [email protected]
