Antoine Pitrou <pit...@free.fr> added the comment: > Another option would be to have the read-end act like a non-blocking > socket (i.e., raise EAGAIN). > > Since it would mostly be for testing, would it make more sense to add > it to test.support or someplace similar instead of io?
I thought it might be useful for third-party libraries, or even non-testing situations (although obviously the latter wouldn't be very common). But, yes, a starting point could be test.support. It would also avoid having to write unit tests and docs :) In this case, I would like to do it as a part of the nntplib patch. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9939> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
