Message 217712 - Python tracker

➜

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
Date	2014-05-01.17:33:35
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAH_1eM2-Lefb-u0t7m62T6sF-2k79BWbukRr+Spqwn-2Eo4YWg@mail.gmail.com>
In-reply-to	<1398946667.03.0.621371730374.issue21406@psf.upfronthosting.co.za>

Content
Enum are for, well, enumerated values, so for values within a finite and known range (like days, cards, etc). OTOH, I'm not sure all socket constants could be categorized like this. 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, I'm not sure how we could categorize them. Unless would declare them all in a "SocketConstant" Enum?

Enum are for, well, enumerated values, so for values within a finite
and known range (like days, cards, etc).
OTOH, I'm not sure all socket constants could be categorized like this.
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, I'm
not sure how we could categorize them.
Unless would declare them all in a "SocketConstant" Enum?

History
Date	User	Action	Args
2014-05-01 17:33:35	neologix	set	recipients: + neologix, barry, pitrou, eli.bendersky, ethan.furman
2014-05-01 17:33:35	neologix	link	issue21406 messages
2014-05-01 17:33:35	neologix	create