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 Alexander.Belopolsky, Arfrever, belopolsky, jcea, khenriksson, larry, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rosslagerwall, skrah, vstinner
Date 2011-09-29.17:47:07
SpamBayes Score 0.004635203
Marked as misclassified No
Message-id <>
> BTW, what is the status of cdecimal?

I just wrote the same in another issue, but not everyone is subscribed
to that:

I think cdecimal is finished and production ready. The version in

is the same as what will be released as cdecimal-2.3 in a couple of
weeks. cdecimal-2.3 has a monumental test suite against *both* and decNumber. The test suite no longer finds any
kind of (unknown) divergence between, cdecimal and

Tests for cdecimal-2.3 have been running on 6 cores for more
than half a year.

In short, review would be highly welcome. ;)
Date User Action Args
2011-09-29 17:47:08skrahsetrecipients: + skrah, loewis, jcea, mark.dickinson, belopolsky, lars.gustaebel, vstinner, larry, nadeem.vawda, Arfrever, r.david.murray, Alexander.Belopolsky, rosslagerwall, khenriksson
2011-09-29 17:47:08skrahsetmessageid: <>
2011-09-29 17:47:07skrahlinkissue11457 messages
2011-09-29 17:47:07skrahcreate