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 gvanrossum, loewis, neologix, pitrou, python-dev, vstinner, yselivanov
Date 2014-07-24.18:55:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406228117.05.0.0644194429676.issue22018@psf.upfronthosting.co.za>
In-reply-to
Content
As I said offline to Victor, I think it would be better to have a single function, i.e. keep set_wakeup_fd(). It makes the API simpler, less confusing and error prone: some people will wonder which one they should use, might end up using the wrong one, or both.
Furthermore, it makes writing portable Python code more difficult, since the user has to chose the right function.
If set_wakeup_fd() can do an fstat() (or whatever that it on Windows) to detect the FD type and call send() instead of write() on a socket, all the above issues would go away.
"Never let the user do what the library can do for him".
History
Date User Action Args
2014-07-24 18:55:17neologixsetrecipients: + neologix, gvanrossum, loewis, pitrou, vstinner, python-dev, yselivanov
2014-07-24 18:55:17neologixsetmessageid: <1406228117.05.0.0644194429676.issue22018@psf.upfronthosting.co.za>
2014-07-24 18:55:17neologixlinkissue22018 messages
2014-07-24 18:55:16neologixcreate