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 Oren Milman
Recipients Oren Milman, amaury.forgeotdarc, benjamin.peterson, martin.panter, pitrou
Date 2017-03-07.01:13:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488849190.34.0.885930733116.issue29741@psf.upfronthosting.co.za>
In-reply-to
Content
I don't have a use case for that. (I noticed this behavior by
chance, while working on some other issue.)

However, IIUC, commit 4fa88fa0ba35e25ad9be66ebbdaba9aca553dc8b,
by Benjamin Peterson, Antoine Pitrou and Amaury Forgeot d'Arc,
includes patching the aforementioned StringIO functions, so that
they would accept integer types.
So I add them to the nosy list, as I guess that the use cases for
accepting integer types in StringIO methods are also use cases
for accepting integer types in BytesIO.

And now that you mention the docs, according to them, both StringIO
and BytesIO inherit these methods from BufferedIOBase or IOBase.
Thus, the methods are already expected to behave the same, aren't
they?
History
Date User Action Args
2017-03-07 01:13:10Oren Milmansetrecipients: + Oren Milman, amaury.forgeotdarc, pitrou, benjamin.peterson, martin.panter
2017-03-07 01:13:10Oren Milmansetmessageid: <1488849190.34.0.885930733116.issue29741@psf.upfronthosting.co.za>
2017-03-07 01:13:10Oren Milmanlinkissue29741 messages
2017-03-07 01:13:09Oren Milmancreate