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 pitrou
Recipients amaury.forgeotdarc, benjamin.peterson, pitrou, stutzbach
Date 2010-09-24.15:59:36
SpamBayes Score 5.2566364e-08
Marked as misclassified No
Message-id <1285343972.3243.21.camel@localhost.localdomain>
In-reply-to <1285343641.59.0.2808290227.issue9939@psf.upfronthosting.co.za>
Content
> 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.
History
Date User Action Args
2010-09-24 15:59:37pitrousetrecipients: + pitrou, amaury.forgeotdarc, benjamin.peterson, stutzbach
2010-09-24 15:59:36pitroulinkissue9939 messages
2010-09-24 15:59:36pitroucreate