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 vstinner
Recipients gvanrossum, loewis, neologix, pitrou, python-dev, vstinner, yselivanov
Date 2014-07-24.10:00:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406196016.97.0.719987691976.issue22018@psf.upfronthosting.co.za>
In-reply-to
Content
> I don't understand this. If you're ok with calling fileno() under Linux, why not under Windows?

I propose to add set_wakeup_socket() for all platforms. This function doesn't really call the fileno() method, it gets the socket file descriptor/socket handle from the C structure.

I explained why I prefer to use an object rather than a number for set_wakeup_socket(). For example, it makes a clear separation between set_wakeup_fd(int) and set_wakeup_socket(socket).

Would you prefer to use the file descriptor/socket handler for set_wakeup_socket()?
History
Date User Action Args
2014-07-24 10:00:17vstinnersetrecipients: + vstinner, gvanrossum, loewis, pitrou, neologix, python-dev, yselivanov
2014-07-24 10:00:16vstinnersetmessageid: <1406196016.97.0.719987691976.issue22018@psf.upfronthosting.co.za>
2014-07-24 10:00:16vstinnerlinkissue22018 messages
2014-07-24 10:00:16vstinnercreate