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 serhiy.storchaka
Recipients martin.panter, r.david.murray, rhettinger, serhiy.storchaka, xiang.zhang
Date 2016-07-22.15:32:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469201522.48.0.768338533468.issue27572@psf.upfronthosting.co.za>
In-reply-to
Content
It looks to me that the support of bytes-like objects besides bytes and bytearray was added accidentally, as a side effect of supporting Unicode. Note, that this support had a bug until issue24802, thus correct support of other bytes-like objects exists less than a year. The option of deprecating other bytes-like objects support looks reasonable to me. Especially in the light of deprecating bytearray paths support (issue26800).

On other side, the need of copying a buffer can be considered as implementation detail, since low-level int parsing functions require NUL-terminated C strings. We can add alternative low-level functions that work with not-NUL-terminated strings. This needs more work.
History
Date User Action Args
2016-07-22 15:32:02serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, r.david.murray, martin.panter, xiang.zhang
2016-07-22 15:32:02serhiy.storchakasetmessageid: <1469201522.48.0.768338533468.issue27572@psf.upfronthosting.co.za>
2016-07-22 15:32:02serhiy.storchakalinkissue27572 messages
2016-07-22 15:32:02serhiy.storchakacreate