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, martin.panter, njs, pitrou, stutzbach, xgdomingo
Date 2018-01-16.08:13:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516090399.83.0.467229070634.issue32561@psf.upfronthosting.co.za>
In-reply-to
Content
> Ideally we would be able to do buffer-only reads through all the of the different read methods (read, readline, readinto, ...),

Hmm... We already have non-blocking support in BufferedIOReader, except it *doesn't work*.  The problem is, the semantics mandated by readline() and even buffered read() don't work very well with non-blocking IO (see issue13322).

So my opinion here is that only raw IO objects (FileIO) should have this functionality.  People can build their own functionality on top of that (such as Tornado or asyncio do with their streams).
History
Date User Action Args
2018-01-16 08:13:19pitrousetrecipients: + pitrou, benjamin.peterson, stutzbach, njs, martin.panter, xgdomingo
2018-01-16 08:13:19pitrousetmessageid: <1516090399.83.0.467229070634.issue32561@psf.upfronthosting.co.za>
2018-01-16 08:13:19pitroulinkissue32561 messages
2018-01-16 08:13:19pitroucreate