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 mark.dickinson
Recipients facundobatista, mark.dickinson, ncoghlan
Date 2008-09-15.15:49:43
SpamBayes Score 5.3727023e-12
Marked as misclassified No
Message-id <1221493785.37.0.981783913878.issue2486@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry for the silence:  new country + new job + no internet connection 
outside work = not many opportunities to spend time on this (or any 
other part of Python) at the moment.

I do now have a version 0.2 of the deccoeff type, and more importantly a 
version of decimal.py that's adapted to use it;  all tests in 
test_decimal.py pass, which is a start.  But there's significant work to 
be done tidying up the code, identifying speed-critical bits, and moving 
those bits from Python to C.

I'm wondering where to post the code;  I could post a tarball here but 
it's a bit unwieldy.  Perhaps it would be worth creating a new branch to 
work on this?

This definitely seems like a (>=) two-person task;  any help would be 
much appreciated!  Thanks Facundo and Nick for comments so far.  I also 
wonder whether there are alternative approaches that might do better.

If we follow this approach, I'm doubtful about doing this for 3.0.1; 
even though the API is unchanged, this seems like too big a change for a 
bugfix release, with too great a risk of breakage.
History
Date User Action Args
2008-09-15 15:49:45mark.dickinsonsetrecipients: + mark.dickinson, facundobatista, ncoghlan
2008-09-15 15:49:45mark.dickinsonsetmessageid: <1221493785.37.0.981783913878.issue2486@psf.upfronthosting.co.za>
2008-09-15 15:49:44mark.dickinsonlinkissue2486 messages
2008-09-15 15:49:43mark.dickinsoncreate