gh-100972: For command line examples in the documentation, use "python" rather than "python3"

[furkanonder]

• Issue: For command line examples in the documentation, use "python" rather than "python3" #100972

[hugovk]

Thanks!

[felixxm]

I don't see much value in changing old release notes.

[vsajip]

Doesn't this assume that the system Python installation will be Python 3.x such that "python" will start a 3.x interpreter? If that's the case, it shouldn't be needed to specify "python3" for "-m venv" usages, right? Also, is it definitely the case that "python" will invoke 3.x on all platforms, old and new? For example I have some (not very) old Ubuntu machines where "python3" is needed. Anyone following along the documentation with this change could run into problems.

[rhettinger]

On my Mac, python no longer refers to an executable. Only python3 works. So, at least for Mac Users, the status quo is better. With the proposed substitutions, the examples won't work any more.

[furkanonder]

On my Mac, python no longer refers to an executable. Only python3 works. So, at least for Mac Users, the status quo is better. With the proposed substitutions, the examples won't work any more.

If there are problems with the Mac, I think this PR should be reverted.

[erlend-aasland]

On my Mac, python no longer refers to an executable. Only python3 works. So, at least for Mac Users, the status quo is better. With the proposed substitutions, the examples won't work any more.

If there are problems with the Mac, I think this PR should be reverted.

I disagree; reverting that PR will only create more churn (both in the git history, but more importantly also by burning CI and contributor time). I'm closing this and the linked issue:

• There is no uncontroversial way to fix this
• Many core devs will categorise spelling fixes (including this) as churn; even more so given there is no consensus