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 Sergey.Kirpichev
Recipients Sergey.Kirpichev, asmeurer, mark.dickinson, rhettinger, tim.peters
Date 2021-03-10.08:53:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <YEiJFY961Ar3IRIs@note>
In-reply-to <1615266669.06.0.0450552948441.issue43420@roundup.psfhosted.org>
Content
On Tue, Mar 09, 2021 at 05:11:09AM +0000, Tim Peters wrote:
> those for + and - are much subtler

In fact, these optimizations will payoff faster (wrt denominators
size), esp. due to gcd==1 branch.

Sorry for off-topic:

> WRT which, I added Python's Karatsuba implementation and regret doing so.
> I don't want to take it out now (it's already in ;-) ), but it added quite
> a pile of delicate code to what _was_ a much easier module to grasp.

(And was much more useless, even as a fallback.

But in the end - I agreed, you can't outperform professional bigint
implementations.  I think, you can _use_ them instead.)

> People who need fast multiplication are still far better off using gmpy2 anyway

(Another strange python "feature", IMHO.  Why the custom bigint
implementation, why not use the project, that run professionals in the
field?  Looking on the issue 21922 - it seems, that small ints
arithmetics can be almost as fast as for python ints.  Is the
memory handling - out-of-memory situation - the only severe problem?)
History
Date User Action Args
2021-03-10 08:53:47Sergey.Kirpichevsetrecipients: + Sergey.Kirpichev, tim.peters, rhettinger, mark.dickinson, asmeurer
2021-03-10 08:53:47Sergey.Kirpichevlinkissue43420 messages
2021-03-10 08:53:46Sergey.Kirpichevcreate