➜

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.

作者 mark.dickinson
收信人 facundobatista, mark.dickinson, rhettinger, skrah
日期 2010-04-27.10:50:31
SpamBayes Score 4.0253634e-11
Marked as misclassified 否
Message-id <1272365433.03.0.752179029322.issue8540@psf.upfronthosting.co.za>
In-reply-to
内容
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.
历史
日期 用户 动作 参数
2010-04-27 10:50:33mark.dickinson修改recipients: + mark.dickinson, rhettinger, facundobatista, skrah
2010-04-27 10:50:33mark.dickinson修改messageid: <1272365433.03.0.752179029322.issue8540@psf.upfronthosting.co.za>
2010-04-27 10:50:31mark.dickinson链接issue8540 messages
2010-04-27 10:50:31mark.dickinson创建