|
|
comp.lang.python |
> On May 26, 2:38 pm, Steven Bethard <steven.beth...@gmail.com> wrote: >> http://www.python.org/dev/peps/pep-0008/ > Really? Underscore-separated words preferred over camel case? What (2) To be consistent with surrounding code that also breaks it Of course, for new code, such as that in this thread, there's no reason STeVe Paul McGuire wrote: Rationale? It's a style guide. There is no rationale. ;-)
> I ***love*** this "10 Little Programs" idea! As soon as I get a
> breathing space, I'm going to add a "10 Little Parsers" page to the
> pyparsing wiki!
>> <nitpick>
>> Though the code should probably follow PEP 8 guidelines, e.g.
>> under_scores instead of camelCase for object and method names:
>> </nitpick>
> is the rationale for this?
> If we want to just say "well, PEP-8 says such and such," I think this I really don't think so. If anything, it's gotten more strict. PEP 8
> is an area where the thinking has possibly evolved since 2001.
used to allow either camelCase or under_scores. Now it only allows the
latter.
> I guess pyparsing with its mixedCase functions and attributes is Many (if not all) of these modules were written before the most recent
> doomed for the Dunce Corner. Too bad for BeautifulSoup, cElementTree,
> and wxPython that are also at variance with this canon of Python
> coding style.
incarnation of PEP 8. Thus, they fall under the second good reason "to
break a particular rule":
to break from the PEP 8 guidelines.