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 foom
Recipients bbangert, foom, giampaolo.rodola, loewis, nicdumz, ronaldoussoren
Date 2010-07-29.20:17:26
SpamBayes Score 0.0006536095
Marked as misclassified No
Message-id <1280434648.4.0.599265452009.issue5154@psf.upfronthosting.co.za>
In-reply-to
Content
The reason it's a problem is because a "device" is everything other than a socket, pipe, slave-side of tty, or file. That is, /dev/null, /dev/zero, /dev/tty, psuedo-tty masters from openpty (e.g. for running subprocesses), etc.

I find it quite amazing that this is still broken after so long. Would it really be that hard for them to unify the select() and poll() code in the kernel? Sigh.

BTW, this same issue also affects kqueue.

But I'd say that Apple's utter failure in writing a working kernel is not really enough reason to disable the poll call for Python. If people want to use it only for the kinds of files that it works for, I don't see why python should prevent that.

Note that in the distant past, poll on OSX was *severely* broken, as it was a userspace wrapper over select(). In those days, disabling it was certainly the right thing to do.
History
Date User Action Args
2010-07-29 20:17:28foomsetrecipients: + foom, loewis, ronaldoussoren, giampaolo.rodola, nicdumz, bbangert
2010-07-29 20:17:28foomsetmessageid: <1280434648.4.0.599265452009.issue5154@psf.upfronthosting.co.za>
2010-07-29 20:17:26foomlinkissue5154 messages
2010-07-29 20:17:26foomcreate