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 methane
Recipients asvetlov, methane, pitrou, vstinner, yselivanov
Date 2017-12-15.09:56:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513331810.28.0.213398074469.issue32331@psf.upfronthosting.co.za>
In-reply-to
Content
Document of socket.type says:

  The socket type.

  https://docs.python.org/3/library/socket.html#socket.socket.type

OK, so, are SOCK_CLOEXEC and SOCK_NONBLOCK socket type?

  These two constants, if defined, can be combined with the socket types and allow you to set some flags atomically...

   https://docs.python.org/3/library/socket.html#socket.SOCK_CLOEXEC

So they are not socket type.  They are constants which can be used for
setting some flags.

Regarding to this document, I think this can be bugfix rather than
behavior change.
History
Date User Action Args
2017-12-15 09:56:50methanesetrecipients: + methane, pitrou, vstinner, asvetlov, yselivanov
2017-12-15 09:56:50methanesetmessageid: <1513331810.28.0.213398074469.issue32331@psf.upfronthosting.co.za>
2017-12-15 09:56:50methanelinkissue32331 messages
2017-12-15 09:56:50methanecreate