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 alexandre.vassalotti
Recipients alexandre.vassalotti
Date 2009-08-11.21:15:29
SpamBayes Score 2.476369e-09
Marked as misclassified No
Message-id <1250025332.91.0.596662376204.issue6687@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation for PyBytes_FromObject states:

.. cfunction:: PyObject* PyBytes_FromObject(PyObject *o)

   Return the bytes representation of object *o* that implements
   the buffer protocol.

However, there exists a special-case for integer object in
PyBytes_FromObject that makes the function return a null-initialized
bytes object. Currently, this is only used for handling `bytes(10)'.

I don't like changing APIs after a stable release, but I believe this
behaviour is error-prone and surprising (and darn right annoying even).
So, I believe the special-case should be made specific to the bytes
constructor.

Thus, here is the fine patch.
History
Date User Action Args
2009-08-11 21:15:33alexandre.vassalottisetrecipients: + alexandre.vassalotti
2009-08-11 21:15:32alexandre.vassalottisetmessageid: <1250025332.91.0.596662376204.issue6687@psf.upfronthosting.co.za>
2009-08-11 21:15:31alexandre.vassalottilinkissue6687 messages
2009-08-11 21:15:31alexandre.vassalotticreate