Message169068
| Author |
eric.araujo |
| Recipients |
asvetlov, eric.araujo, georg.brandl, pitrou, python-dev, stefanholek, vinay.sajip |
| Date |
2012年08月24日.18:47:06 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1345834027.05.0.0431802979866.issue15776@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> 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. |
|