[issue23202] pyvenv does not fail like documented when a venv already exists

2015-01-23 Thread Vinay Sajip
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

[issue23202] pyvenv does not fail like documented when a venv already exists

2015-01-23 Thread Roundup Robot
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 -

[issue23202] pyvenv does not fail like documented when a venv already exists

2015-01-08 Thread Florian Bruhin
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