➜

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 ncoghlan
Recipients docs@python, eli.bendersky, ethan.furman, georg.brandl, giampaolo.rodola, ncoghlan
Date 2014-01-25.07:49:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390636158.8.0.990095342557.issue20386@psf.upfronthosting.co.za>
In-reply-to
Content 
Sorry, I misread Giampaolo's example as indicating that socket.SocketType wasn't there at all in Python 3.3. However, it's there, and with the same name as in Python 2, so I agree this is a regression.

I suggest socket.SocketKind as an alternate name for the enumeration that avoids the name clash, but we also need a test case that ensures that socket.SocketType has the correct value.
History
Date User Action Args
2014-01-25 07:49:18ncoghlansetrecipients: + ncoghlan, georg.brandl, giampaolo.rodola, eli.bendersky, docs@python, ethan.furman
2014-01-25 07:49:18ncoghlansetmessageid: <1390636158.8.0.990095342557.issue20386@psf.upfronthosting.co.za>
2014-01-25 07:49:18ncoghlanlinkissue20386 messages
2014-01-25 07:49:18ncoghlancreate