RetroSearch Browse

Sat Feb 21 20:28:21 CET 2015 · https://mail.python.org/pipermail/python-dev/2015-February/138410.html

/* Namespaces are one honking great idea -- let's do more of those! */

There are two ways to avoid name conflicts: prefixes and namespaces. 
Programming languages that lacks namespaces (such as C) need to use 
prefixes. For example: PROTOCOL_SSLv2, PROTOCOL_SSLv3, PROTOCOL_SSLv23. 
Python used the same prefixed names when reflect C constants to module 
level Python globals. But when convert integer constants to IntEnum, is 
it needed to preserve common prefix? Or may be we can drop it, because 
enum class name plays its role?

class Protocol(IntEnum):
     PROTOCOL_SSLv2 = ...
     PROTOCOL_SSLv3 = ...
     PROTOCOL_SSLv23 = ...

or

class Protocol(IntEnum):
     SSLv2 = ...
     SSLv3 = ...
     SSLv23 = ...

? Protocol.PROTOCOL_SSLv2 or Protocol.SSLv2?

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

Showing content from https://mail.python.org/pipermail/python-dev/2015-February/138410.html below:

[Python-Dev] Prefixes and namespaces