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_venv

This will allow me to skip my next command that I usually always do:
/tmp/awesome_venv/bin/pip install --upgrade pip setuptools

Thoughts? If people are happy, I will look at doing the PR. 

I would envision I'll either import (which seems to be a no no from pip maintainers) the upgrade code or just fork pip ...

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 forking, I would expect this could just be done by invoking the venv's pip as a subprocess.

Also, it would need to be a different flag than `--upgrade`, which already exists.

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 or fork to run the child process/command, so that's what I wished to communicate via the term 'fork'.

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

Can this issue be closed now?

I believe so - Would love it could be included with latest 3.8 or is there no chance of that?

> 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.

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 CLI argument that does nothing unless specified, I can’t really see any disadvantages of merging this into 3.8. Is there any way other than discussing with the release manager to have this considered?

> Is there any way other than discussing with the release manager to have this considered?

I don't believe so.

New changeset 1cba1c9abadf76f458ecf883a48515aa3b534dbd by Shantanu in branch 'master':
bpo-34556: Document addition of upgrade_deps to venv.create (GH-20135)
https://github.com/python/cpython/commit/1cba1c9abadf76f458ecf883a48515aa3b534dbd

I noticed this new feature was not added to the Python 3.9 what's new: https://docs.python.org/3.9/whatsnew/3.9.html#venv

Should it be?