Message 70981 - Python tracker

➜

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	georg.brandl, loewis, mgiuca, orsenthil
Date	2008-08-10.12:45:14
SpamBayes Score	0.006758514
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
So I assumed. In that case, why is there a "fromhex"? (Was that put in there before the notion of transform/untransform?) As I've been saying, it's weird to have a fromhex but not a tohex. Anyway, assuming we go to 3.1 and add transform/untransform, I suppose fromhex will remain for backwards, and tohex will not be needed. So I guess this issue is closed.

So I assumed.

In that case, why is there a "fromhex"? (Was that put in there before
the notion of transform/untransform?) As I've been saying, it's weird to
have a fromhex but not a tohex.

Anyway, assuming we go to 3.1 and add transform/untransform, I suppose
fromhex will remain for backwards, and tohex will not be needed. So I
guess this issue is closed.

History
Date	User	Action	Args
2008-08-10 12:45:15	mgiuca	set	recipients: + mgiuca, loewis, georg.brandl, orsenthil
2008-08-10 12:45:15	mgiuca	set	messageid: <[email protected]>
2008-08-10 12:45:14	mgiuca	link	issue3532 messages
2008-08-10 12:45:14	mgiuca	create