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

[Christian Tismer]

Yes, you can do the upgrade, but there are a few flaws which keep me 
from using this:

It is pretty common to use virtualenv inside a mercurial checkout.

With venv, installation with

     python3 -m venv my-repos

complains that the directory is not empty.
With

     python3 -m venv my-repos --clear

I was shocked, because that kills my repository :-(
After doing a new clone of my repos, I tried with

     python3 -m venv my-repos --update

This works a little, but does not install the bin/activate source.

Finally, I reverted to using virtualenv instead, although I would love
to migrate. But this is not enough.

Anything I'm missing here?

cheers - chris

On 24.08.12 13:30, Andrew Svetlov wrote:
> Looks like you can use for that
> $ pyvenv . --upgrade
>
>
> On Fri, Aug 24, 2012 at 12:19 PM, "Stefan H. Holek · Jarn"
> <stefan at jarn.com> wrote:
>> FYI, I have created a tracker issue for this: http://bugs.python.org/issue15776
>>
>> Stefan
>>
>>
>> On 23.07.2012, at 09:09, Stefan H. Holek wrote:
>>
>>> The feature certainly is on *my* wish-list but I might be alone here. ;-)

-- 
Christian Tismer             :^)   <mailto:tismer at stackless.com>
Software Consulting          :     Have a break! Take a ride on Python's
Karl-Liebknecht-Str. 121     :    *Starship* http://starship.python.net/
14482 Potsdam                :     PGP key -> http://pgp.uni-mainz.de
phone +49 173 24 18 776  fax +49 (30) 700143-0023
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
       whom do you want to sponsor today?   http://www.stackless.com/