Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-July/121037.html below:

[Python-Dev] Why no venv in existing directory?

• Previous message: [Python-Dev] [Python-checkins] cpython: Close #15387: inspect.getmodulename() now uses a new
• Next message: [Python-Dev] Why no venv in existing directory?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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 at epy.co.at

• Previous message: [Python-Dev] [Python-checkins] cpython: Close #15387: inspect.getmodulename() now uses a new
• Next message: [Python-Dev] Why no venv in existing directory?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4