Nick Coghlan <[EMAIL PROTECTED]> added the comment: 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? _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2486> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
