This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients asvetlov, eric.araujo, georg.brandl, pitrou, python-dev, stefanholek, vinay.sajip
Date 2012-08-24.18:54:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345834240.3368.13.camel@localhost.localdomain>
In-reply-to <>
Le vendredi 24 août 2012 à 18:47 +0000, Éric Araujo a écrit :
> Éric Araujo added the comment:
> > Well, changing it to do that means changing functionality, which is
> disallowed at this point in the release process.
> I think people used to “virtualenv .” can see this as a regression
> between virtualenv and pyvenv, but if the PEP did not list that use
> case then it’s too late.  I’d suggest we even back out the “pyvenv
> --clear .” commit, which did not address the needs of the
> “virtualenv .” users.

Agreed with Eric. The feature could be added correctly in 3.4.
Date User Action Args
2012-08-24 18:54:02pitrousetrecipients: + pitrou, georg.brandl, vinay.sajip, eric.araujo, asvetlov, stefanholek, python-dev
2012-08-24 18:54:02pitroulinkissue15776 messages
2012-08-24 18:54:02pitroucreate