A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-December/059318.html below:

[Python-Dev] Naming conventions in Py3K

[Python-Dev] Naming conventions in Py3K [Python-Dev] Naming conventions in Py3K"Martin v. Löwis" martin at v.loewis.de
Fri Dec 30 11:40:50 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.  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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4