[Python-Dev] (class) module names clarification (original) (raw)
François Pinard pinard at iro.umontreal.ca
Fri Mar 19 10:07:19 EST 2004
- Previous message: [Python-Dev] (class) module names clarification
- Next message: [Python-Dev] Joys of Optimization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Greg Ewing]
"Jewett, Jim J" <jim.jewett at eds.com>:
> from userlist import UserList > from stringio import StringIO
That's actually an excellent argument for this convention. It would have been good to have socket.Socket, too.
All these would be good news indeed.
On the other hand, while I think Guido is right in saying it was a
mistake to use hairy capitalisation in module names, he could go a bit
further and declare that good module names should ideally not be
simple English words, which users would likely keep for themselves,
as simple variable names. In that vein, userlist', stringio' and
heapq' are good names for a module, while string' and socket' are less welcome. It would be so nice writing socket = [...].Socket()'!
-- François Pinard http://www.iro.umontreal.ca/~pinard
- Previous message: [Python-Dev] (class) module names clarification
- Next message: [Python-Dev] Joys of Optimization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]