[issue38483] [venv] Add ~/.venvrc to change module defaults

Change by Cooper Lees : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue38483] [venv] Add ~/.venvrc to change module defaults

Cooper Lees added the comment: 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

[issue38483] [venv] Add ~/.venvrc to change module defaults

Brett Cannon added the comment: Is this best served in the stdlib or in an external tool like how virtualenvwrapper is separate from virtualenv? While I get the convenience of not having to install another tool to do this, it does bring in some complexity that does not directly tie into the

[issue38483] [venv] Add ~/.venvrc to change module defaults

Cooper Lees added the comment: Updated PR to use venv.ini. Will fix any CI errors encountered. -- ___ Python tracker ___ ___

[issue38483] [venv] Add ~/.venvrc to change module defaults

Eryk Sun added the comment: In Windows, dot files cannot be hidden (i.e. set the hidden file attribute), unlike how they're conventionally hidden in Unix. Doing so breaks normal access. A directory such as ".venv" can be hidden, but that's still going against convention. For Windows, I

[issue38483] [venv] Add ~/.venvrc to change module defaults

Cooper Lees added the comment: Good point. Happy to match the virtualenv module and use `.ini` if others agree. -- ___ Python tracker ___

[issue38483] [venv] Add ~/.venvrc to change module defaults

Laurie Opperman added the comment: ".xrc" usually means a file to be run (by a shell) at shell start, and therefore is a script of command to run ("rc" seems to come from "runcom", ie run commands). INI files usually have a ".ini" or ".cfg" suffix. `virtualenv`, for example, used an

[issue38483] [venv] Add ~/.venvrc to change module defaults

Change by Karthikeyan Singaravelan : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38483] [venv] Add ~/.venvrc to change module defaults

Change by Karthikeyan Singaravelan : -- pull_requests: -16359 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38483] [venv] Add ~/.venvrc to change module defaults

Change by Cooper Lees : -- pull_requests: +16359 pull_request: https://github.com/python/cpython/pull/168 ___ Python tracker ___

[issue38483] [venv] Add ~/.venvrc to change module defaults

Change by Cooper Lees : -- keywords: +patch pull_requests: +16358 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16802 ___ Python tracker ___

[issue38483] [venv] Add ~/.venvrc to change module defaults

New submission from Cooper Lees : 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