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 vinay.sajip
Recipients asvetlov, georg.brandl, stefanholek, vinay.sajip
Date 2012-08-24.12:50:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345812658.58.0.151575585015.issue15776@psf.upfronthosting.co.za>
In-reply-to
Content
Venvs should be regarded as throwaway; there is really no reason to add other files (e.g. project files) to venvs.

Two common patterns are:

1. Use a single place for all venvs (virtualenvwrapper does this)
2. Use a venv in a subdirectory of a project directory

The current implementation follows PEP 405, and the functionality was discussed on python-dev before being finalised.
History
Date User Action Args
2012-08-24 12:50:58vinay.sajipsetrecipients: + vinay.sajip, georg.brandl, asvetlov, stefanholek
2012-08-24 12:50:58vinay.sajipsetmessageid: <1345812658.58.0.151575585015.issue15776@psf.upfronthosting.co.za>
2012-08-24 12:50:58vinay.sajiplinkissue15776 messages
2012-08-24 12:50:57vinay.sajipcreate