RetroSearch Browse

Tue Aug 29 09:59:08 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-August/068510.html

Steve Holden wrote:

> Standards, apparently, are for *other* people :-)

ET was written years before the "certain modules should use camelcase" stuff
was removed from PEP 8.  as a refresher for those of you who have trouble
remembering how things were back in early 2004, here's GvR's original style
guide:

    http://www.python.org/doc/essays/styleguide/

    Modules that export a single class (or a number of closely related
    classes, plus some additional support) are often named in MixedCase,
    with the module name being the same as the class name (e.g. the
    standard StringIO module). Modules that export a bunch of functions
    are usually named in all lowercase. /.../

    There is an emerging convention that when an extension module written
    in C or C++ has an accompanying Python module that provides a higher
    level (e.g. more object oriented) interface, the Python module's name
    CapWords, while the C/C++ module is named in all lowercase and has a
    leading underscore (e.g. Tkinter/_tkinter).

</F> 

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-August/068510.html below:

[Python-Dev] Doc suggestion for Elementtree (for 2.5? a bitlate, I know...)