[issue23202] pyvenv does not fail like documented when a venv already exists
Vinay Sajip added the comment: The behaviour was changed in 3.4 in response to #15776, but the documentation wasn't updated to match. I will update the docs to remove the reference to the error. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23202 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23202] pyvenv does not fail like documented when a venv already exists
Roundup Robot added the comment: New changeset a3a44d871d70 by Vinay Sajip in branch 'default': Closes #23202: pyvenv documentation updated to match its behavior. https://hg.python.org/cpython/rev/a3a44d871d70 -- nosy: +python-dev resolution: - fixed stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23202 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23202] pyvenv does not fail like documented when a venv already exists
New submission from Florian Bruhin: https://docs.python.org/3/library/venv.html says: If the target directory already exists an error will be raised, unless the --clear or --upgrade option was provided. However, that doesn't seem to be the case: [florian@ginny ~]$ python --version Python 3.4.2 [florian@ginny ~]$ pyvenv foobar [florian@ginny ~]$ ls foobar bin include lib lib64 pyvenv.cfg [florian@ginny ~]$ pyvenv foobar [florian@ginny ~]$ -- components: Library (Lib) messages: 233718 nosy: The Compiler, vinay.sajip priority: normal severity: normal status: open title: pyvenv does not fail like documented when a venv already exists type: behavior versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23202 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
