[Python-Dev] Why no venv in existing directory? (original) (raw)

Carl Meyer carl at oddbird.net
Thu Jul 19 18:39:31 CEST 2012

Hi Stefan,

On 07/19/2012 06:28 AM, Stefan H. Holek wrote:

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.

I'd have no problem with lifting the restriction.

I don't recall any clear rationale; I think it was probably just the simplest implementation initially, and no one ever raised it as an issue in the PEP process.

Carl

More information about the Python-Dev mailing list