m.faassen at vet.uu.nl
Sat Feb 22 10:48:52 CET 2003
I present to you all PEP 3008: Underscore/Camelcase insensitivity. Guido
is entirely tired of this debate and asked me to make a posting about it
here so that comp.lang.python can decide.
Many people use camelCase for method names, others use under_scores. Some
people like myself find ourselves switching between the two, not
knowing which to prefer. Plus, beginners can forget to spell it under_score
and accidentally use camelCase and vice versa, which is not a good thing.
Guido is asking you all to discuss this proposal, come up with other
proposals and a voting procedure, and then the voting result.
The following proposal is made:
can be called like this:
but under the new PEP 3008 rules, also like this:
And likewise, the following definition:
can be called also using its underscore equivalent:
Of course this also works for attributes:
will do exactly the same thing.
Functions and methods which would have the same name under the new rule
simply have the last definition win; it is not expected there are many
instances of this case but Python will issue a CamelUnderscoreWarning if
they are encountered.
History of the 20th Century: WW1, WW2, WW3?
No, WWW -- Could we be going in the right direction?
More information about the Python-list