Author alexandre.vassalotti
Recipients alexandre.vassalotti, benjamin.peterson, mark.dickinson
Date 2009-12-11.13:54:19
SpamBayes Score 1.70902e-12
Marked as misclassified No
Message-id <1260539661.7.0.919931740491.issue6687@psf.upfronthosting.co.za>
In-reply-to
Content
Mark Dickinson wrote:
> Is there still a need for a separate C function for creating a zero-
> initialized bytes object from a Py_ssize_t or a Python integer?

What C function are you referring to?

> And this check doesn't cover other, similar, cases: for example, list('')
> will still be converted by PyBytes_FromObject, while list('123') won't.

Well, one is a just empty list and the other a list of strings. I don't see
why converting a empty list to bytes should raise an error. Although I agree
the type check is a bit out of place, I think it will help prevents bugs. 

In addition, PyBytes_FromObject() is documented as equivalent to the
built-in
bytes(). Since calling bytes() with any unicode string raises a TypeError
exception, unless an encoding is specified, I believe PyBytes_FromObject()
should also follow this convention.
History
Date User Action Args
2009-12-11 13:54:21alexandre.vassalottisetrecipients: + alexandre.vassalotti, mark.dickinson, benjamin.peterson
2009-12-11 13:54:21alexandre.vassalottisetmessageid: <1260539661.7.0.919931740491.issue6687@psf.upfronthosting.co.za>
2009-12-11 13:54:20alexandre.vassalottilinkissue6687 messages
2009-12-11 13:54:19alexandre.vassalotticreate