➜

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 eric.araujo
Recipients asvetlov, eric.araujo, georg.brandl, pitrou, python-dev, stefanholek, vinay.sajip
Date 2012-08-24.17:00:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345827604.11.0.851498685682.issue15776@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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

I’m a recent virtualenv user, but before I became a virtualenvwrapper fan I used to create venvs in the project top-level directory (typically a Mercurial clone root), using “virtualenv .”.
History
Date User Action Args
2012-08-24 17:00:04eric.araujosetrecipients: + eric.araujo, georg.brandl, vinay.sajip, pitrou, asvetlov, stefanholek, python-dev
2012-08-24 17:00:04eric.araujosetmessageid: <1345827604.11.0.851498685682.issue15776@psf.upfronthosting.co.za>
2012-08-24 17:00:03eric.araujolinkissue15776 messages
2012-08-24 17:00:03eric.araujocreate