I notice that most(all?) of those are from pretty old modules, which explains the "old", pre PEP-8 names.
I think it would be good to clean this up with a set of aliases -- but it is a fair bit of code-churn for not much real gain. I guess it comes down to:
How much maintenance do those modules see anyway? Are they changing much, if at all between recent versions?
How often to "end users" use them -- as opposed to using high level packages on top of them? What I'm getting at here is that it's a lot more important that a newbie or casual scripter gets consistent names than for package maintainers.
On Thu, Dec 5, 2019 at 1:32 PM Matthias Bussonnier email@example.com wrote:
Thanks for pointing those out.
At least when the alias is
error = OtherName the text is the stack
Python-ideas mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://firstname.lastname@example.org/message/JSHM7F... Code of Conduct: http://python.org/psf/codeofconduct/
-- Christopher Barker, PhD
Python Language Consulting