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 loewis
Recipients arjennienhuis, benjamin.peterson, eric.smith, loewis, vstinner
Date 2009-07-11.16:47:34
SpamBayes Score 6.44563e-10
Marked as misclassified No
Message-id <>
In-reply-to <>
> hex(10) returns '0xa' instead of 'a'.

Ah, right. So I would still use


rather than the format builtin format function. Actually, I would
probably use

  ('%x' % len(bytes)).encode("ascii")

> The point is that need to convert to ascii for each int that you send.
> You cannot just wrap the socket with an encoding. This makes porting
> difficult.

This I don't understand. What porting becomes more difficult?
From 2.x to 3.x? Why do you have any .format calls in your code that you
want to port - .format was only added in 2.6, so if you want to support
2.x, you surely are not using .format, are you?
Date User Action Args
2009-07-11 16:47:35loewissetrecipients: + loewis, vstinner, eric.smith, benjamin.peterson, arjennienhuis
2009-07-11 16:47:34loewislinkissue3982 messages
2009-07-11 16:47:34loewiscreate