➜

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 glyph
Recipients arjennienhuis, benjamin.peterson, christian.heimes, eric.smith, exarkun, ezio.melotti, flox, glyph, gvanrossum, loewis, martin.panter, pitrou, serhiy.storchaka, terry.reedy, uau, vstinner
Date 2013-01-23.19:00:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <45DF3CF9-A60E-4DC3-B961-31DD9753DB73@twistedmatrix.com>
In-reply-to <1358935090.79.0.979595193234.issue3982@psf.upfronthosting.co.za>
Content 
On Jan 23, 2013, at 1:58 AM, Antoine Pitrou <report@bugs.python.org> wrote:

> Numbers currently don't have a __bytes__ method:
> 
>>>> (5).__bytes__()
> Traceback (most recent call last):
>  File "<stdin>", line 1, in <module>
> AttributeError: 'int' object has no attribute '__bytes__'

They do have some rather odd behavior when passed to the builtin though:

>>> bytes(10)
b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'

It would be much more convenient for me if bytes(int) returned the ASCIIfication of that int; but honestly, even an error would be better than this behavior.  (If I wanted this behavior - which I never have - I'd rather it be a classmethod, invoked like "bytes.zeroes(n)".)
History
Date User Action Args
2013-01-23 19:00:46glyphsetrecipients: + glyph, gvanrossum, loewis, terry.reedy, exarkun, pitrou, vstinner, eric.smith, christian.heimes, benjamin.peterson, ezio.melotti, arjennienhuis, flox, uau, martin.panter, serhiy.storchaka
2013-01-23 19:00:46glyphlinkissue3982 messages
2013-01-23 19:00:46glyphcreate