Title: pyvenv does not fail like documented when a venv already exists
Type: behavior Stage: resolved
Components: Library (Lib) Versions: Python 3.4
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: The Compiler, python-dev, vinay.sajip
Priority: normal Keywords:

Created on 2015-01-09 06:02 by The Compiler, last changed 2015-01-23 19:37 by python-dev. This issue is now closed.

Messages (3)
msg233718 - (view) Author: Florian Bruhin (The Compiler) * Date: 2015-01-09 06:02 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 ~]$
msg234572 - (view) Author: Vinay Sajip (vinay.sajip) * (Python committer) Date: 2015-01-23 19:24
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.
msg234573 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2015-01-23 19:37
New changeset a3a44d871d70 by Vinay Sajip in branch 'default':
Closes #23202: pyvenv documentation updated to match its behavior.
Date User Action Args
2015-01-23 19:37:19python-devsetstatus: open -> closed

nosy: + python-dev
messages: + msg234573

resolution: fixed
stage: resolved
2015-01-23 19:24:52vinay.sajipsetmessages: + msg234572
2015-01-09 06:02:04The Compilercreate