This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients barry, eli.bendersky, ethan.furman, neologix, pitrou, r.david.murray
Date 2014-05-01.19:58:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1VkrHCCsb-Pmfb4kg7fJUb2v4buitt6G+kWB-HyPkk3A@mail.gmail.com>
In-reply-to <CAH_1eM0CA0Bi60kC7dOkb+S5g+PamJ4_LdJapY2aO0zdxq9VHQ@mail.gmail.com>
Content
To put it slightly differently:
AF_XXX constant actually whome belong to the same namespace, the
socket address family namespace.
So we put them all in AddressFamily Enum.

Now, for many constants defined in system header files, it's not so
clear, e.g. BTPROTO_RFCOMM, TIPC_ADDR_ID, SCM_CREDENTIALS: in which
Enum would you declare them?

I'm not saying it's a bad idea: it actually probably makes sense for
e.g. socket-level options (SO_REUSEADDR & Co), but it don't see any
generic classification scheme that would make sense for all of them.
History
Date User Action Args
2014-05-01 19:58:53neologixsetrecipients: + neologix, barry, pitrou, r.david.murray, eli.bendersky, ethan.furman
2014-05-01 19:58:53neologixlinkissue21406 messages
2014-05-01 19:58:53neologixcreate