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 benjamin.peterson, pitrou, stutzbach
Date 2010-09-24.15:19:20
SpamBayes Score 1.7790782e-05
Marked as misclassified No
Message-id <1285341562.44.0.992846065146.issue9939@psf.upfronthosting.co.za>
In-reply-to
Content
While writing tests for nntplib, it came to me that a PipeIO or BytesPipeIO would be useful (I actually wrote a minimal one). It would be a non-seekable in-memory bytes buffer with distinct read and write pointers, so as to act like a system FIFO or a socket.makefile() object. A pure Python implementation would probably be sufficient, since the main use would be for test purposes. What do you think?

(you may point to os.pipe() but it has problems such as limited buffer size: try to write many bytes to the write end and it will block until the other end tries to read something)
History
Date User Action Args
2010-09-24 15:19:22pitrousetrecipients: + pitrou, benjamin.peterson, stutzbach
2010-09-24 15:19:22pitrousetmessageid: <1285341562.44.0.992846065146.issue9939@psf.upfronthosting.co.za>
2010-09-24 15:19:21pitroulinkissue9939 messages
2010-09-24 15:19:20pitroucreate