Author mark.dickinson
Recipients facundobatista, mark.dickinson, rhettinger, skrah
Date 2010-04-27.10:50:31
SpamBayes Score 4.02536e-11
Marked as misclassified No
Message-id <1272365433.03.0.752179029322.issue8540@psf.upfronthosting.co.za>
In-reply-to
Content
Re: ExtendedContext, the comments in decimal.py say:

# Pre-made alternate contexts offered by the specification
# Don't change these; the user should be able to select these
# contexts and be able to reproduce results from other implementations
# of the spec.

This doesn't make a lot of sense to me, since (as Stefan says) the choice of precision 9 doesn't seem to come from the specification.

However, the current ExtendedContext is used extensively in doctests and elsewhere;  it would be awkward to change it now.  I think adding the IEEE formats and encouraging users to use those in place of ExtendedContext might be the best bet.

I'd also still want to make _clamp public in this case, to avoid people wondering why two apparently identical contexts (one with _clamp=1, one with _clamp=0) can lead to different results.
History
Date User Action Args
2010-04-27 10:50:33mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, facundobatista, skrah
2010-04-27 10:50:33mark.dickinsonsetmessageid: <1272365433.03.0.752179029322.issue8540@psf.upfronthosting.co.za>
2010-04-27 10:50:31mark.dickinsonlinkissue8540 messages
2010-04-27 10:50:31mark.dickinsoncreate