Chris Angelico <ros...@gmail.com>: > Python has a facility like this. It doesn't namespace the keywords, > but it does let you choose whether to have them or not. In Python 2.5, > you could type "from __future__ import with_statement" to turn 'with' > into a keyword. After Python 2.6, it's always a keyword.
That certainly softens the blow but might still cause unnecessary suffering when maintaining/resurrecting legacy Python code. How about blocking the introduction of new keywords for ever except if you specify: from __py35__ import syntax Eventually, every Python module would likely begin with a statement like that, and it would document the assumption more clearly than __future__. Marko -- https://mail.python.org/mailman/listinfo/python-list
