Message169070
| 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 |
<1345834027.05.0.0431802979866.issue15776@psf.upfronthosting.co.za> |
| Content |
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. |
|