[Python-Dev] Naming conventions in Py3K (original) (raw)

Ka-Ping Yee python-dev at zesty.ca
Fri Dec 30 12:14:31 CET 2005

Brett Cannon wrote:

I am fine with changing the built-in types, but changing the built-in singletons just looks really odd to me. So odd that I just don't want to see them changed. I mean when I think of constants, I think of a variable that references an object and that reference never changes. The built-ins you are referencing, though, are singletons: named objects that are not variables.

In behaviour and intended usage, they are much more like constants than like classes, though.

So keeping their naming scheme as-is does not feel like a breaking of the rules to me since they are not treated the same (especially at the C level).

I don't know if we share the same philosophy on this, but i don't think the C level should play a big role here -- the names in Python programs should express how something works (and more importantly how it is intended to be used) at the Python level, not details under the hood.

On Fri, 30 Dec 2005, "Martin v. Löwis" wrote:

Actually, I thought some of them would become reserved words in P3k, anyway.

That would be cool. If so, it would make sense for them to be all in lowercase.

-- ?!ng

More information about the Python-Dev mailing list