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 facundobatista, mark.dickinson, rhettinger, skrah
Date 2010-04-27.10:15:53
SpamBayes Score 0.0031093098
Marked as misclassified No
Message-id <1272363355.68.0.960088801616.issue8540@psf.upfronthosting.co.za>
In-reply-to
Content
Hmm.  Yes, the spec itself is rather vague on the subject of clamping, so I withdraw my claim that clamping is necessary for compliance with the spec.  It *is* necessary to make the those testcases with 'clamp=1' pass, though.

So from the point of view of compliance with the specification it's fine to leave the _clamp attribute private.

I agree it would be useful to give easy access to the IEEE 754 formats, though, for interoperability with C and Java (thanks for the Java link!).  The most important formats are decimal32, decimal64 and decimal128, but IEEE 754 also specifies parameters for decimal{k} where k is any multiple of 32 bits.
History
Date User Action Args
2010-04-27 10:15:55mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, facundobatista, skrah
2010-04-27 10:15:55mark.dickinsonsetmessageid: <1272363355.68.0.960088801616.issue8540@psf.upfronthosting.co.za>
2010-04-27 10:15:54mark.dickinsonlinkissue8540 messages
2010-04-27 10:15:53mark.dickinsoncreate