classification
Title: venv docs - doesn't match behavior
Type: Stage:
Components: Documentation Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, jason.coombs
Priority: normal Keywords:

Created on 2018-01-12 18:07 by jason.coombs, last changed 2018-01-12 18:07 by jason.coombs.

Messages (1)
msg309867 - (view) Author: Jason R. Coombs (jason.coombs) * (Python committer) Date: 2018-01-12 18:07
In the docs for the venv command, it states:

> Changed in version 3.4: In earlier versions, if the target directory already existed, an error was raised, unless the --clear or --upgrade option was provided. Now, if an existing directory is specified, its contents are removed and the directory is processed as if it had been newly created.

However, that's not the behavior I observe:

$ python -m venv env
$ env/bin/pip install -q requests
$ python -m venv env          
$ env/bin/python -c "import requests"
$

Plus, I believe the _current_ behavior should be documented not in a 'change' note. I suggest the change note should read:

> Changed in version 3.4: In earlier versions, if the target directory already existed, an error was raised, unless the --clear or --upgrade option was provided.

And the third paragraph, following "It also creates an (initially empty...Lib\site-packages).":

> If an existing directory is specified, it will be re-used.
History
Date User Action Args
2018-01-12 18:07:13jason.coombscreate