Uh oh!
There was an error while loading. Please reload this page.
gh-80642: timeit - Additional changes for autorange - #12954
gh-80642: timeit - Additional changes for autorange#12954alessandrocucci wants to merge 7 commits into
Conversation
- have `timeit` and `repeat` methods (and functions) fall back on `autorange` if the number is set to 0 or None.
Uh oh!
There was an error while loading. Please reload this page.
bsolomon1124
commented
May 12, 2019
Was there consideration given to adding Since |
that was not discussed in issue36461 |
bsolomon1124
commented
May 13, 2019
Actually, looking at things more carefully, I don't think it's necessary, since it looks like |
Carreau
commented
May 25, 2019
if i understand this correctly |
alessandrocucci
commented
May 25, 2019
There is a proposal to rename it to "target_time", as Steven wrote in https://bugs.python.org/issue36461 |
rhettinger
commented
May 10, 2022
ISTM that almost the entire point of having autorange() was to avoid the need for configuration. |
iritkatriel
left a comment
There was a problem hiding this comment.
This has merge conflicts now.
bedevere-bot
commented
Dec 6, 2022
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
StanFromIreland
commented
Oct 18, 2025
This PR has been stale for over three years, closing in favour of #140283 |
timeitandrepeatmethods (and functions) fall backon
autorangeif the number is set to 0 or None.https://bugs.python.org/issue36461