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 martin.panter
Recipients Henning.von.Bargen, benjamin.peterson, docs@python, martin.panter, pitrou, r.david.murray, serhiy.storchaka
Date 2016-04-12.13:25:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After thinking about Issue 26720 (see also Issue 15994), I think it might be worth documenting not only that bytes-like objects may be passed, but in some cases the class should not be access the object after the method returns. This applies to at least RawIOBase.readinto() and especially RawIOBase.write(). If you want to save the write() data in memory, you have to make a copy, because the original may be lost when BufferedWriter overwrites its internal buffeer.
Date User Action Args
2016-04-12 13:25:06martin.pantersetrecipients: + martin.panter, pitrou, benjamin.peterson, r.david.murray, docs@python, serhiy.storchaka, Henning.von.Bargen
2016-04-12 13:25:06martin.pantersetmessageid: <>
2016-04-12 13:25:06martin.panterlinkissue20699 messages
2016-04-12 13:25:06martin.pantercreate