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 corona10, mark.dickinson, pablogsal, serhiy.storchaka, vstinner
Date 2020-10-01.16:26:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1601569604.6.0.641123320205.issue41902@roundup.psfhosted.org>
In-reply-to
Content
> Do we need another fast-path in long_div(a, b) when b == _PyLong_One? Just return a in this case.

I'd much prefer not. Every extra fast path check costs time for the general case, and there's no strong reason to expect people to be dividing by one. The range code seems like the right place for this optimization, not the long-divide code.
History
Date User Action Args
2020-10-01 16:26:44mark.dickinsonsetrecipients: + mark.dickinson, vstinner, serhiy.storchaka, corona10, pablogsal
2020-10-01 16:26:44mark.dickinsonsetmessageid: <1601569604.6.0.641123320205.issue41902@roundup.psfhosted.org>
2020-10-01 16:26:44mark.dickinsonlinkissue41902 messages
2020-10-01 16:26:44mark.dickinsoncreate