Facundo Batista <[EMAIL PROTECTED]> added the comment: Nick said:
> So I would suggest either a new directory in the sandbox, or > re-using Facundo's original directory (which includes the > telco benchmark) +1 > 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 I'm not seeing this job as a way to solve the 3.0 slowdown, but more as the way to slowly, but steadily, replace parts of Decimal from Python to C as needed. So, I'm +1 to target this to 3.1, and I'm -0 to register the slowdown in the releases notes (those who use Decimal aren't really in it for speed...). Thank you!! _______________________________________ 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
