Fix cmdline doc to make '-m timeit' consistent with other parts of th…

[jgors]

…e docs.

The syntax in the cmdline documentation is confusing regarding the -m timeit code. In the timeit documentation it always shows the command line invocation as python -m timeit, so this is just a very simple PR to keep the docs consistent throughout.

[the-knights-who-say-ni]

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@jgors

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

[eamanu]

IMO this PR doesn't get any improve on the documentation. python -mtimeit work successfully.

BTW, @jgors don't forget sign CLA

[jgors]

IMO this PR doesn't get any improve on the documentation. python -mtimeit work successfully.

I noticed that it works before submitting the PR, but it seems odd to me. Just like this works, python -c"print('Hi')", but it definitely seems strange when there isn't a space between the arg and what's being passed to it, like: python -c "print('hello')". Also, I tried pip and it works with same way -- with pip install -rrequirements.txt behaving exactly like pip install -r requirements.txt). This behavior seems puzzling.

Think of *nix commands. For example, rm. When you want to pass several args at once, you can either list them separately (e.g. rm -f -i myfile.py) or concatenate them together (e.g. rm -fi myfile.py), but rm fails if you were to call the command without a space between the argument(s) and the file to be removed (e.g.rm -fimyfile.py).

It's not really clear why this command line behavior in python would be intentional. Even though it currently works as is, it's not obvious as to why this is (or should be) the case.

I created an issue for this.

[rougeth]

I believe the consistence by itself already is a good argument for the PR. @jgors as Ned wrote at the issue, have you seen other cases that needs update?

[iritkatriel]

Thanks, @jgors. This was already fixed here #18853