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 mark.dickinson
Recipients eric.smith, hardkrash, mark.dickinson
Date 2010-03-05.09:38:47
SpamBayes Score 3.5213525e-06
Marked as misclassified No
Message-id <1267781929.88.0.873811329379.issue8062@psf.upfronthosting.co.za>
In-reply-to
Content
How common is this 'common practice'?  Could you point to some publicly available examples? Are there other languages that have built-in facilities for dealing with hexadecimal representations of integers in this way?

I think I've seen hex strings separated by spaces every four digits, and by spaces or colons every two digits (though the latter was usually used for something that's better seen as a sequence of bytes rather than a hexadecimal representation of a large integer).  I've rarely seen the underscore separation that you describe, but perhaps that's because I haven't been looking in the right places.

Do you have a concrete proposal for amending the formatting mini-language syntax to support this?  Perhaps you could run this past the python-ideas mailing list to try to get support and to thrash out the details of a possible specification?

To me this seems to be adding yet more complication to an already complicated formatting mini-language for something that few people will ever need, so I'd be -1 on this as it stands.
History
Date User Action Args
2010-03-05 09:38:50mark.dickinsonsetrecipients: + mark.dickinson, eric.smith, hardkrash
2010-03-05 09:38:49mark.dickinsonsetmessageid: <1267781929.88.0.873811329379.issue8062@psf.upfronthosting.co.za>
2010-03-05 09:38:48mark.dickinsonlinkissue8062 messages
2010-03-05 09:38:47mark.dickinsoncreate