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 christian.heimes, mark.dickinson, terry.reedy, tim.peters
Date 2009-12-23.15:33:46
SpamBayes Score 2.60993e-08
Marked as misclassified No
Message-id <1261582433.15.0.849644454059.issue1811@psf.upfronthosting.co.za>
In-reply-to
Content
Here's an updated patch, against py3k.  On my machine, a/b is a touch faster with this patch when abs(a), 
abs(b) are smaller than 1e15 or so;  it's (inevitably) slower than the existing implementation for larger a 
and b.  For 'random' a and b, average running time is proportional to the size of b, and is independent of 
the size of a;  worst-case running time (which occurs when a has many trailing zero bits) grows as 
max(size(a), size(b)).

Changing versions to 2.7 and 3.2, but I'm mostly aiming for 3.2.  It may not be worth backporting to 2.7, 
given the extra effort required to deal correctly with ints as well as with longs.
History
Date User Action Args
2009-12-23 15:33:54mark.dickinsonsetrecipients: + mark.dickinson, tim.peters, terry.reedy, christian.heimes
2009-12-23 15:33:53mark.dickinsonsetmessageid: <1261582433.15.0.849644454059.issue1811@psf.upfronthosting.co.za>
2009-12-23 15:33:51mark.dickinsonlinkissue1811 messages
2009-12-23 15:33:51mark.dickinsoncreate