Bugs item #757365, was opened at 2003-06-19 18:35 Message generated for change (Settings changed) made by birkenfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=757365&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Python 2.3 >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Duncan Grant (duncangrantuk) Assigned to: Nobody/Anonymous (nobody) Summary: FutureWarning: %u/%o/%x/%X of negative int will return a sig Initial Comment: printf style formatting: "FutureWarning: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up" The library reference clearly states that these are UNSIGNED representations, so the Futurewarning must be spurious! Please tell me you don't really intend to break this in 2.4 !!!! In 20+ yrs of low level bit-twiddling I have never ever wanted a signed hexadecimal. The idea of a signed hex or octal is just plain stupid. ---------------------------------------------------------------------- >Comment By: Reinhold Birkenfeld (birkenfeld) Date: 2005-05-31 13:30 Message: Logged In: YES user_id=1188172 Now that this has already been "broken", the bug can be closed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=757365&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
