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 Aur.Saraf
Recipients Aur.Saraf, christian.heimes, gregory.p.smith, python-dev, tarek
Date 2022-03-16.02:21:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1647397283.85.0.45925942384.issue45150@roundup.psfhosted.org>
In-reply-to
Content
The rationale behind `from_raw_file()` and the special treatment of non-buffered IO is that there is no `read_buffer()` API or other clean way to say "I want to read just what's currently in the buffer so that from now on I could read directly from the file descriptor without harm".

If you want to read from a buffered file object, sure, just call `from_file()`. If you want to ensure you'll get full performance benefits, call `from_raw_file()`. If you pass an eligible file object to `from_file()` you'll get the benefits anyway, because why not.
History
Date User Action Args
2022-03-16 02:21:23Aur.Sarafsetrecipients: + Aur.Saraf, gregory.p.smith, christian.heimes, tarek, python-dev
2022-03-16 02:21:23Aur.Sarafsetmessageid: <1647397283.85.0.45925942384.issue45150@roundup.psfhosted.org>
2022-03-16 02:21:23Aur.Saraflinkissue45150 messages
2022-03-16 02:21:23Aur.Sarafcreate