Message178656
| Author |
neologix |
| Recipients |
Erez.Sh, William.Edwards, asksol, danken, dmalcolm, giampaolo.rodola, jnoller, neologix, pitrou, sbt, synapse, vstinner |
| Date |
2012年12月31日.09:36:39 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAH_1eM3-SOV76h-V4FoW_YV3CiqesV-hV2SVVn8dkySN9DetjQ@mail.gmail.com> |
| In-reply-to |
<1356729955.63.0.103457964326.issue10527@psf.upfronthosting.co.za> |
| Content |
The patch looks good, however there's something really bothering me:
in issue #14635, the same type of patch was applied to telnetlib,
here, it's multiprocessing and AFAICT, any single use of select() in
the standard library is subject to this FD_SETSIZE limitation.
That why I think it could probably be a good idea to expose a
high-level "selector" object in the select module, which would use the
"right" syscall transparently (e.g. select, poll or /dev/poll), with a
unified API. This would make writing portable and efficient I/O
multiplexing code much easier, not only in the stdlib, but also for
end-users. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年12月31日 09:36:39 | neologix | set | recipients:
+ neologix, pitrou, vstinner, giampaolo.rodola, jnoller, synapse, asksol, dmalcolm, danken, Erez.Sh, sbt, William.Edwards |
| 2012年12月31日 09:36:39 | neologix | link | issue10527 messages |
| 2012年12月31日 09:36:39 | neologix | create |
|