Message 354712 - Python tracker

➜

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	cooperlees
Date	2019-10-15.10:51:40
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
In-reply-to

Content
I'd like to propose adding a run commands (.venvrc) file support to the venv library. File Location: `~/.venvrc` This file will support all current CLI arguments and override the defaults for each CLI if present in the file. I will also endeavour to add test for POSIX + Windows systems. I propose using `configparser` and an `.ini` style config for the `.venvrc`. My main use for this is to allow myself to default to always using `--upgrade-deps` when I create new venvs. Thoughts? Concerns?

I'd like to propose adding a run commands (.venvrc) file support to the venv library.

File Location: `~/.venvrc`

This file will support all current CLI arguments and override the defaults for each CLI if present in the file. I will also endeavour to add test for POSIX + Windows systems.

I propose using `configparser` and an `.ini` style config for the `.venvrc`.

My main use for this is to allow myself to default to always using `--upgrade-deps` when I create new venvs.

Thoughts? Concerns?

History
Date	User	Action	Args
2019-10-15 10:51:40	cooperlees	set	recipients: + cooperlees
2019-10-15 10:51:40	cooperlees	set	messageid: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
2019-10-15 10:51:40	cooperlees	link	issue38483 messages
2019-10-15 10:51:40	cooperlees	create