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 orsenthil
Recipients loewis, mgiuca, orsenthil
Date 2008-08-10.08:15:01
SpamBayes Score 0.000726318
Marked as misclassified No
Message-id <>
* scriptor Matt Giuca, explico 
> I think the biggest problem I have is the existence of fromhex. It's
> really strange/inconsistent to have a fromhex without a tohex.

Except, when we look at the context. This is bytes class
method returns a bytes or bytearray object, decoding the given string object.

Do we require an opposite in the bytes class method? Where will we use it?
> Also I think a lot of people (like me, in my relative inexperience) are
> going to be at a loss as to why .encode('hex') went away, and they'll

No, it is not going away. str.encode('hex') is available to users when they
seek it. They wont look for it under bytes type.
Date User Action Args
2008-08-10 08:15:17orsenthilsetrecipients: + orsenthil, loewis, mgiuca
2008-08-10 08:15:01orsenthillinkissue3532 messages
2008-08-10 08:15:01orsenthilcreate