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 cooperlees
Recipients Epic_Wink, brett.cannon, cooperlees, eryksun, vinay.sajip
Date 2019-11-23.03:27:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574479672.64.0.514859779623.issue38483@roundup.psfhosted.org>
In-reply-to
Content
I vote in the stdlib. This is the biggest win of venv over virtualenv The aim of this request is to allow developers to customize some of the venv defaults to make it easier to move from project to project.

To ensure a clean development environment, some days I create multiple venvs (virtual environments) a day. I treat my venv's ephemeral, and I am sure many other do too. Being able to set `--upgrade-deps` and/or other defaults via a config file just saves a few more key strokes and allows Python to be even more delightful to develop in over other languages.

In regards to you bringing up pyenv.cfg + metadata, this attacks a totally different problem. This is allowing developers to set some defaults for venv creation. It does not change any internal meta data and is just an optional optimization developers can choose to use.
History
Date User Action Args
2019-11-23 03:27:52cooperleessetrecipients: + cooperlees, brett.cannon, vinay.sajip, eryksun, Epic_Wink
2019-11-23 03:27:52cooperleessetmessageid: <1574479672.64.0.514859779623.issue38483@roundup.psfhosted.org>
2019-11-23 03:27:52cooperleeslinkissue38483 messages
2019-11-23 03:27:52cooperleescreate