[issue34556] Add --upgrade to venv module

Cooper Lees added the comment: That’s very disappointing. I had the very small PR ready to merge ~3 weeks before beta1. I now have to wait ~1.5years to be able to use this anywhere that I won’t be back porting it. I am happy to be on the hook and forward fix anything it causes, but as a new

[issue34556] Add --upgrade to venv module

Vinay Sajip added the comment: > included with latest 3.8 or is there no chance of that? Unfortunately not, I think, as it missed the cut for 3.8beta1. Never mind! Thanks for your contribution. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions:

[issue34556] Add --upgrade to venv module

Cooper Lees added the comment: I believe so - Would love it could be included with latest 3.8 or is there no chance of that? -- ___ Python tracker ___ ___

[issue34556] Add --upgrade to venv module

Vinay Sajip added the comment: Can this issue be closed now? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue34556] Add --upgrade to venv module

Łukasz Langa added the comment: New changeset 4acdbf11b1fae1af24c47413a6caa593010d1b6f by Łukasz Langa (Cooper Lees) in branch 'master': bpo-34556: Add --upgrade-deps to venv module (#13100) https://github.com/python/cpython/commit/4acdbf11b1fae1af24c47413a6caa593010d1b6f -- nosy: +l

[issue34556] Add --upgrade to venv module

Change by Cooper Lees : -- keywords: +patch pull_requests: +13013 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue34556] Add --upgrade to venv module

Cooper Lees added the comment: Thanks for hi-lighting, yes, sorry. I should of been clearer here. What should we use other than `--upgrade`? I just wanted the topic to be generic: - `-U` - `--upgrade-modules` - `--pip-upgrade` - `--pull-latest` In regards to using subprocess, it calls exec o

[issue34556] Add --upgrade to venv module

Zachary Ware added the comment: This sounds good to me; my `python -m venv venv` commands are also almost always followed up by `venv/bin/python -m pip install -U pip setuptools wheel`. I wouldn't get the `wheel` from this, but it's not always necessary anyway. Rather than importing or fork

[issue34556] Add --upgrade to venv module

New submission from Cooper Lees : I'd like to propose add a `--upgrade` to venv module to automatically update pip and potentially setuptools if supplied. This will allow ensuring you have the latest and greatest of these core components. Example Usage: python3 -m venv --upgrade /tmp/awesome_