Can "quit" be made to quit?

You might be surprised if you saw some of the questions I close on Stack Overflow on a daily basis.

The argument isn’t that it’s unreasonable to need parens to call the quit function; the argument is that it’s unreasonable to need to call a function in order to quit the interpreter. After all, you didn’t write Python code to start the interpreter, either. If we are going to reinforce the understanding that the interpreter is a separate program that sits outside of the code being typed in, and interprets pieces of it one at a time (as opposed to how a script works), it stands to reason that this same program should accept other interactions, too. random and len are operating on existing Python objects; quit conceptually is operating on the interpreter. (help is a less clear-cut case; it can be envisioned either way.)

I think the proposal is predicated upon forming this distinction, yes.

I am, consequent to the above, serious about it, and I understand that it takes time to deprecate things that way. (Better, IMO, than being super-strict about semver and blowing up the version number to 100+ like web browsers do nowadays - since it doesn’t work anyway.)

That said, several alternate proposals ITT also make sense - including the “just change the string to be more regular and less presumptive” one.