Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork201
Enable decimal_pi benchmark in the suite (MANIFEST)#453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
They were not added here inpython#341 for no reasons.
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
hugovk commentedJan 19, 2026 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
cc@mdboom in case there was a reason to omit them. |
skirpichev commentedJan 20, 2026
Ah, pypy3 failure seems relevant. decimal_factorial looks too slow on PyPy3 (with only pure-Python version of the decimal module). |
Uh oh!
There was an error while loading.Please reload this page.
skirpichev commentedJan 28, 2026
@hugovk, anything else? I think we can enable decimal_factorial test, but this will need a workaround for pure-Python decimal module. The presence of accelerated module we can detect, trying to import the
|
They were not added here in#341 for no reasons.