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 vstinner
Recipients docs@python, jneb, mark.dickinson, serhiy.storchaka, skrah, vstinner
Date 2016-02-03.09:51:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"It's great to have this stuff, but I don't think it belongs in core Python: I'd much rather that the core Python integer implementation remain simple, portable and low-maintenance, and work well for the domain it's intended for: small-to-medium size integers."

Yeah I agree. Maybe we need to explain that somewhere? In the devguide? Even in Python doc?

I know that they are super crazy^W fast algorithm to handle very large numbers (hum, what is large? more than 4096 bits?), but they are usually very complex.

Projects like GMP have ultra fast code with optimizations in assemblers. Having assembler implementation is clearly out of the scope of Python.

"Maybe I should change the issue then to "documentation missing": it nowhere says in the documentation that decimal has optimized multiprecision computations."

Well, nowhere means:

Usually, we don't document performances of a function, maybe only its complexity.


You may move to the numpy community which is problably more keen on such optimization than the Python *core*.
Date User Action Args
2016-02-03 09:51:53vstinnersetrecipients: + vstinner, jneb, mark.dickinson, skrah, docs@python, serhiy.storchaka
2016-02-03 09:51:53vstinnersetmessageid: <>
2016-02-03 09:51:53vstinnerlinkissue26256 messages
2016-02-03 09:51:53vstinnercreate