My armchair analysis of this today has exposed, to me, the serious risks of bikeshedding[0] taken to an extreme. So much contentious debate about 1-3 character syntax preferences. The consequences from the debate being deeply more impactful than any of the proposed options in the first place.

0: https://en.wikipedia.org/wiki/Law_of_triviality

This cracked me up:

"Python has different operators for bitwise and logical operations which C should copy (already copied with iso646.h except if you try to use them, men will stop shaking hands with you)."

Slightly related: I noticed the other day that VS Code does not highlight and, or, et al. as keywords in a C++ program.

They have a list of proposals for syntax, but "as" keyword isn't there. In the last thread I saw, people claimed that it would be confusing in the with-statement, but I have a hard time seeing why. In a with statement, the context manager in my eyes is a property of the with-statement, not the as-statement. You're basically doing `with fp = open():`. Does anyone have a good example of why "as" was a bad candidate?

And Van Rossum has just quit without naming a successor or giving any guidance on how python should be governed!

https://www.mail-archive.com/python-committers@python.org/ms...