I think the discussion is coming to a clear conclusion here not to do this (except for the standard library classes like anydbm.error). I'm piping in with my own -1 (for all the sane reasons) to hopefully stop this thread quickly. We don't need more noise here.
--Guido On 12/29/05, Ka-Ping Yee <[EMAIL PROTECTED]> wrote: > In a fair number of cases, Python doesn't follow its own recommended > naming conventions. Changing these things would break backward > compatibility, so they are out of the question for Python 2.*, but > it would be nice to keep these in mind for Python 3K. > > Constants in all caps: > NONE, TRUE, FALSE, ELLIPSIS > > Classes in initial-caps: > Object, Int, Float, Str, Unicode, Set, List, Tuple, Dict, > and lots of classes in the standard library, e.g. > anydbm.error, csv.excel, imaplib.error, mutex.mutex... > > I know these probably look a little funny now to most of us, as > we're used to looking at today's Python (they even look a little > funny to me) but i'm pretty convinced that consistency will be > better in the long run. > > > -- ?!ng > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com