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 asvetlov
Recipients asvetlov, georg.brandl, stefanholek, vinay.sajip
Date 2012-08-24.12:42:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345812174.35.0.325267716661.issue15776@psf.upfronthosting.co.za>
In-reply-to
Content
I don't like current --clear behavior, it's really useless because now venv just deletes everything from virtual environment.
You lose not only virtual env but files from your project also.
virtualenv cleans only <env>/Lib directory, that's much better.

I think venv --clear should cleanup everything which it creates (I mean bin/include/lib for Posix and Scripts/Include/Lib for Windows). Not sure about pyvenv.cfg
History
Date User Action Args
2012-08-24 12:42:54asvetlovsetrecipients: + asvetlov, georg.brandl, vinay.sajip, stefanholek
2012-08-24 12:42:54asvetlovsetmessageid: <1345812174.35.0.325267716661.issue15776@psf.upfronthosting.co.za>
2012-08-24 12:42:53asvetlovlinkissue15776 messages
2012-08-24 12:42:53asvetlovcreate