On 9/5/20 1:18 AM, Jeffrey Kintscher wrote:
My point was that importing "everything" into the global namespace
The only global namespace in Python is builtins [1]. Everything else is module or local.
and then finding that a new version of Python has a new global symbol that causes a symbol conflict in your code is not a reason to reject the change.
Actually, it is. The benefit has to be pretty big to overcome backwards compatibility concerns.
If you use a problematic practice and a change to Python causes a symbol conflict for you, that's on you, not Python.
An officially supported practice that is broken by Python is on Python. Again, the benefits would have to outweigh the code breakage.
-- ~Ethan~ [1] `globals()` actually returns the module namespace. _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/FUIROFYWS7KLS26BI4TKILI26FFQ75YX/ Code of Conduct: http://python.org/psf/codeofconduct/
