[issue21643] "File exists" error during venv --upgrade

Roundup Robot added the comment: New changeset 27e1b4a9de07 by Vinay Sajip in branch '3.4': Issue #21643: Updated test and fixed logic bug in lib64 symlink creation. http://hg.python.org/cpython/rev/27e1b4a9de07 New changeset 71eda9bd8875 by Vinay Sajip in branch 'default': Closes #21643: Merged

[issue21643] "File exists" error during venv --upgrade

STINNER Victor added the comment: Ok, this bug is a regression introduced in Python 3.4.1. -- nosy: +larry priority: normal -> release blocker ___ Python tracker ___

[issue21643] "File exists" error during venv --upgrade

STINNER Victor added the comment: Oh, my test lacks a unit test! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue21643] "File exists" error during venv --upgrade

STINNER Victor added the comment: Full traceback (I modified venv/__main__.py): haypo@smithers$ /opt/py34/bin/python3 -m venv --upgrade ENV Error: [Errno 17] File exists: '/home/haypo/ENV/lib' -> '/home/haypo/ENV/lib64' Traceback (most recent call last): File "/opt/py34/lib/python3.4/runpy.py"

[issue21643] "File exists" error during venv --upgrade

Virgil Dupras added the comment: I could reproduce the bug on the v3.4.1 tag, on the 3.4 branch and on the default branch. I think that one of the conditions for the bug to arise is to have the "lib64" symlink created (as described in #21197). I reproduced the bug on Gentoo and Arch environmen

[issue21643] "File exists" error during venv --upgrade

Senthil Kumaran added the comment: I could not reproduce this in 3.4 / 3.5 [localhost 21643]$ ./python.exe Tools/scripts/pyvenv --upgrade usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear] [--upgrade] [--without-pip] ENV_DIR [ENV_DIR ...] venv: e

[issue21643] "File exists" error during venv --upgrade

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue21643] "File exists" error during venv --upgrade

New submission from Virgil Dupras: There seems to have been a regression in Python 3.4.1 with "pyvenv --upgrade", and this regression seems to be caused by #21197. It now seems impossible to use the "--upgrade" flag without getting a "File exists" error. Steps to reproduce: $ pyvenv env $ pyv