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 scoder
Recipients BreamoreBoy, lemburg, pitrou, scoder
Date 2010-08-20.21:01:37
SpamBayes Score 6.1092755e-06
Marked as misclassified No
Message-id <1282338099.18.0.69433419695.issue7415@psf.upfronthosting.co.za>
In-reply-to
Content
When I read the comments and exception texts in the function, it didn't occur to me that "char buffer" could have been used as a name for the old Py2 buffer interface. From the context, it totally makes sense to me that the function (which decodes a byte sequence into a unicode string) complains about not getting a "bytes object or char buffer" as input. Admittedly, this might sound slightly different when read in Python space.
History
Date User Action Args
2010-08-20 21:01:39scodersetrecipients: + scoder, lemburg, pitrou, BreamoreBoy
2010-08-20 21:01:39scodersetmessageid: <1282338099.18.0.69433419695.issue7415@psf.upfronthosting.co.za>
2010-08-20 21:01:37scoderlinkissue7415 messages
2010-08-20 21:01:37scodercreate