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 skrah
Recipients facundobatista, mark.dickinson, rhettinger, skrah
Date 2010-05-22.10:11:27
SpamBayes Score 0.06673552
Marked as misclassified No
Message-id <1274523089.36.0.922670045114.issue8540@psf.upfronthosting.co.za>
In-reply-to
Content
I'm busy implementing the IEEE754 contexts for cdecimal. To keep things
in sync, it would be nice to agree how they should be created.


Suggestions:

1) c = Decimal64Context

2) c = Context(Decimal64)

3) ?


I have a preference for 2). It's clear that you get a new Object and
the user does not have to wonder if a template context will be
contaminated when using setcontext(Decimal64Context).

(I know there are measures against that, but setcontext( Context(Decimal64))
is explicit rather than implicit.)
History
Date User Action Args
2010-05-22 10:11:30skrahsetrecipients: + skrah, rhettinger, facundobatista, mark.dickinson
2010-05-22 10:11:29skrahsetmessageid: <1274523089.36.0.922670045114.issue8540@psf.upfronthosting.co.za>
2010-05-22 10:11:27skrahlinkissue8540 messages
2010-05-22 10:11:27skrahcreate