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 pitrou
Recipients barry, eli.bendersky, ethan.furman, neologix, pitrou, r.david.murray
Date 2014-05-01.19:54:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398974086.96.0.146752059121.issue21406@psf.upfronthosting.co.za>
In-reply-to
Content
> It makes sense for address families, especially since they're used so
> much, but when it comes to e.g. SO_REUSEADDR or BTPROTO_RFCOMM,

Hmm, I was thinking mostly about protocol numbers. All the BTPROTO_* constants should be part of a given enum (BlueToothProtocol?), the CAN_* constants part of another one.
History
Date User Action Args
2014-05-01 19:54:47pitrousetrecipients: + pitrou, barry, r.david.murray, eli.bendersky, neologix, ethan.furman
2014-05-01 19:54:46pitrousetmessageid: <1398974086.96.0.146752059121.issue21406@psf.upfronthosting.co.za>
2014-05-01 19:54:46pitroulinkissue21406 messages
2014-05-01 19:54:46pitroucreate