[Python-Dev] Naming conventions in Py3K (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Fri Dec 30 11:40:50 CET 2005
- Previous message: [Python-Dev] Naming conventions in Py3K
- Next message: [Python-Dev] Naming conventions in Py3K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. 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).
Actually, I thought some of them would become reserved words in P3k, anyway.
Regards, Martin
- Previous message: [Python-Dev] Naming conventions in Py3K
- Next message: [Python-Dev] Naming conventions in Py3K
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]