Why no venv in existing directory?
19 Jul
2012
19 Jul
'12
2:28 p.m.
Hi All, While trying 3.3 beta I found that I cannot use my favorite virtualenv pattern with pyvenv: $ virtualenv . Installing.....done. $ pyvenv . Error: Directory exists: /Users/stefan/sandbox/foo I appreciate that this behavior is documented and was in the PEP from the start: "If the target directory already exists an error will be raised, unless the --clear or --upgrade option was provided." Still, I am curious what the rationale behind this restriction is. For me, being able to "bless" an existing directory with a virtualenv has always been one of its attractions. Thanks, Stefan -- Stefan H. Holek stefan@epy.co.at
4117
Age (days ago)
4289
Last active (days ago)
8 comments
7 participants
participants (7)
-
"Stefan H. Holek · Jarn" -
Andrew Svetlov -
Carl Meyer -
Christian Tismer -
Stefan H. Holek -
Vinay Sajip -
Łukasz Langa