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 mgiuca
Recipients loewis, mgiuca
Date 2008-08-10.02:47:47
SpamBayes Score 0.00064324
Marked as misclassified No
Message-id <>
You did the 3.1 thing again! We can accept a new feature like this
before 3.0b3, can we not?

> Hmm. There are probably many modules that you haven't used yet.

Snap :)

Well, I didn't know about the community's preference for functions over
methods. You make a lot of good points.

I think the biggest problem I have is the existence of fromhex. It's
really strange/inconsistent to have a fromhex without a tohex.

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
easily be able to find .tohex (by typing help(bytes), or just guessing),
while binascii.hexlify is sufficiently obscure that I had to ask.
Date User Action Args
2008-08-10 02:47:52mgiucasetrecipients: + mgiuca, loewis
2008-08-10 02:47:52mgiucasetmessageid: <>
2008-08-10 02:47:48mgiucalinkissue3532 messages
2008-08-10 02:47:47mgiucacreate