Currently when you execute pyvenv the help message is wrong:

host@~  $ pyvenv
usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]
            [--upgrade] [--without-pip]
            ENV_DIR [ENV_DIR ...]
venv: error: the following arguments are required: ENV_DIR

Based on the docs on https://docs.python.org/3/library/venv.html it should be:

host@~  $ pyvenv
usage: pyvenv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]
              [--upgrade] [--without-pip]
              ENV_DIR [ENV_DIR ...]
pyvenv: error: the following arguments are required: ENV_DIR

Basically instead of saying usage venv it should say usage pyvenv but if you execute the module it should be venv:

host@~  $ python3.5 -m venv
usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]
            [--upgrade] [--without-pip]
            ENV_DIR [ENV_DIR ...]
venv: error: the following arguments are required: ENV_DIR

Patch that solves the issue.

I am on Misc/ACKS on branch 3.4 but not on default branch. I would appreciate if that gets merged to be added :)

Could you please write an unit test for non-regression?

Added tests (hope is what you expect) and changed some bits on the test file to be pep8 comliant.

Thanks for the suggestion, but

(a) I don't think it's worth making this change.
(b) Your change still won't do the right thing in all cases.
(c) Your approach (of passing a parameter just for this) doesn't feel right.

For example, what if pyvenv is invoked using a symlink such as pyvenv-3.4? Your code would say "pyvenv", which seems "just as wrong" as saying "venv".

I don't believe the current state of affairs is really confusing (it hasn't been brought up before) - and even if it is, the right fix seems to be to mention in the documentation that the usage statement may vary slightly depending on exactly how the venv functionality is invoked.

So, do you think that maybe adding something to the documentation. Or we just leave it as it is?

I will add to the documentation, and leave this issue open till I've done that.

> Added tests (hope is what you expect) and changed some bits on the test file to be pep8 comliant.

Nooo, please don't change two things in same patch: open a new issue for your PEP 8 changes.

thanks for the comments.
@haypo I'll add a new one for the pep8 fixes, sorry.
@vinay.sajip I would like to help and try to do the change myself, if this is ok with you

> I would like to help and try to do the change myself

You mean the documentation change? Go right ahead! Just make the change to the 3.4 branch, and I will ensure it's merged into the default branch (3.5). Have you completed a contributor form, as a matter of interest?

From your question, yes I have completed the form.
I've added a new patch just with the documentation change and changing the output from the help command as it was wrong. If it doesn't make sense do let me know. I've done it from 3.4

New changeset 751910294200 by Vinay Sajip in branch 'default':
Closes #23357: Updated documentation on creating venvs.
https://hg.python.org/cpython/rev/751910294200