On Fri, Dec 6, 2019 at 1:02 PM Guido van Rossum <[email protected]> wrote <snip>
> check that there are no *other* classes in a module that also use a > lowercase naming convention (if there are, that module needs more thought > before we change just the exception name). > I expect that will be quite common — older code commonly uses lower case class names — including core built is, of course. We’ve gotten used to that, so I’m not sure it’s worth worrying about. It would still be helpful to clean up the exception names. And changing core class names is a lot more churn. Not that there’s anything wrong with more thought. -CHB > It may also be a good idea to create bugs for each module with a brief > description and tagging it as "Easy" or "Easy (C)" (if there's C code > involved). > > > On Fri, Dec 6, 2019 at 11:02 AM Christopher Barker <[email protected]> > wrote: > >> 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. >> >> -CHB >> >> >> >> On Thu, Dec 5, 2019 at 1:32 PM Matthias Bussonnier < >> [email protected]> wrote: >> >>> Thanks for pointing those out. >>> >>> At least when the alias is `error = OtherName` the text is the stack >>> trace are informative. >>> -- >>> M >>> _______________________________________________ >>> Python-ideas mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> https://mail.python.org/mailman3/lists/python-ideas.python.org/ >>> Message archived at >>> https://mail.python.org/archives/list/[email protected]/message/JSHM7FGTJA7CSCUVZFLKYYFMS3DU7NKB/ >>> Code of Conduct: http://python.org/psf/codeofconduct/ >>> >> >> >> -- >> Christopher Barker, PhD >> >> Python Language Consulting >> - Teaching >> - Scientific Software Development >> - Desktop GUI and Web Development >> - wxPython, numpy, scipy, Cython >> _______________________________________________ >> Python-ideas mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> https://mail.python.org/mailman3/lists/python-ideas.python.org/ >> > Message archived at >> https://mail.python.org/archives/list/[email protected]/message/USDR4AFSJYDPE4GK5MUZQ6JBJ3U2X3KA/ > > >> Code of Conduct: http://python.org/psf/codeofconduct/ >> > > > -- > --Guido van Rossum (python.org/~guido) > *Pronouns: he/him **(why is my pronoun here?)* > <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/> > -- Christopher Barker, PhD Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython
_______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/IEEUEXXHUCETYQ2R6KGW37NHBDLQMAAI/ Code of Conduct: http://python.org/psf/codeofconduct/
