[Python-Dev] Naming conventions in Py3K
Ka-Ping Yee
python-dev at zesty.ca
Fri Dec 30 12:10:10 CET 2005
On Fri, 30 Dec 2005, Reinhold Birkenfeld wrote:
> Ka-Ping Yee wrote:
> > Constants in all caps:
> > NONE, TRUE, FALSE, ELLIPSIS
>
> That's ugly.
I know it looks ugly to you now. But there's a good reason why we use
capitalization for class names -- anyone reading code who comes across
a CapitalizedName can be reasonably certain that it refers to a class.
It's a helpful way to express the intended usage. And, like it or not,
None, True, False, and Ellipsis aren't classes.
> In fact, I like it that the basic Python functions
I didn't say anything about renaming functions. Functions in lowercase
are one of the naming conventions that Python does follow consistently.
> and most of the types are all-lowercase.
That's just not true, though. (Or at least it depends on what you mean
by "most" and by "types".) The types in the built-in module are in
lowercase, and the vast majority of the other types aren't.
-- ?!ng
More information about the Python-Dev
mailing list