RetroSearch Browse

Sun Jan 6 19:22:37 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-January/123472.html

Minor correction:

On 06.01.13 19:10, Christian Tismer wrote:
> 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
>

Sorry, I meant

     python3 -m venv my-repos --upgrade

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

-- 
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/

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

Showing content from https://mail.python.org/pipermail/python-dev/2013-January/123472.html below:

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