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 giampaolo.rodola
Recipients docs@python, eli.bendersky, ethan.furman, georg.brandl, giampaolo.rodola, ncoghlan
Date 2014-01-25.20:00:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390680029.01.0.141914739739.issue20386@psf.upfronthosting.co.za>
In-reply-to
Content
> Please find a better name for the type enum and document the new enums.

Why should new enums be documented and how are they useful?
IMO socket module adopted enum module only to provide a better representation of AF_* and SOCK_* constants on repr(), which is fine.
The fact that in order to do that enum module forces you to create a container is incidental and should not result in polluting socket module API (which is already pretty crowded).
In summary I'd be for renaming those enums to _SocketType and _AddressFamily.
History
Date User Action Args
2014-01-25 20:00:29giampaolo.rodolasetrecipients: + giampaolo.rodola, georg.brandl, ncoghlan, eli.bendersky, docs@python, ethan.furman
2014-01-25 20:00:29giampaolo.rodolasetmessageid: <1390680029.01.0.141914739739.issue20386@psf.upfronthosting.co.za>
2014-01-25 20:00:28giampaolo.rodolalinkissue20386 messages
2014-01-25 20:00:28giampaolo.rodolacreate