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 ncoghlan
Recipients facundobatista, mark.dickinson, ncoghlan
Date 2008-09-15.21:07:18
SpamBayes Score 9.779132e-08
Marked as misclassified No
Message-id <1221512900.43.0.882635114442.issue2486@psf.upfronthosting.co.za>
In-reply-to
Content
This is the kind of project where the sandbox is useful - Facundo's
original decimal work was done there, as was the attempt at a complete
rewrite of the decimal module in C (which turned out to be a less than
optimal approach to the speed problem).

So I would suggest either a new directory in the sandbox, or re-using
Facundo's original directory (which includes the telco benchmark)

http://svn.python.org/view/sandbox/trunk/decimal

And I agree that it is far more sensible to target 2.7/3.1 at this stage
- the 3.0 slowdown, while real, actually isn't as bad as I expected, and
even if it's large enough to be unacceptable to heavy users of Decimal,
the only consequence is that they will have to hold off on migrating to
3.x for 12-18 months.

Should we add something specific to the 3.0 release notes pointing out
that there is approximately a 25% slowdown in the decimal module
relative to 2.x?
History
Date User Action Args
2008-09-15 21:08:20ncoghlansetrecipients: + ncoghlan, facundobatista, mark.dickinson
2008-09-15 21:08:20ncoghlansetmessageid: <1221512900.43.0.882635114442.issue2486@psf.upfronthosting.co.za>
2008-09-15 21:07:19ncoghlanlinkissue2486 messages
2008-09-15 21:07:18ncoghlancreate