[issue18588] timeit examples should be consistent

Roundup Robot added the comment: New changeset c39457a07caa by Ezio Melotti in branch '3.4': #18588: update the timeit examples to be consistent. http://hg.python.org/cpython/rev/c39457a07caa New changeset 45b208ae9eab by Ezio Melotti in branch 'default': #18588: merge with 3.4. http://hg.python

[issue18588] timeit examples should be consistent

Ezio Melotti added the comment: Examples updated, thanks for the report! -- resolution: -> fixed stage: -> resolved status: open -> closed versions: -Python 2.7 ___ Python tracker ___

[issue18588] timeit examples should be consistent

Ezio Melotti added the comment: I tried to run those timings again and the values I got from the terminal are close to the ones I got from the interactive interpreter. I'm not sure why when I wrote those examples I got such different values. It would be fine with me to update them and avoid conf

[issue18588] timeit examples should be consistent

Raymond Hettinger added the comment: > I did find it somewhat confusing when trying to interpret > the timeit documentation. Perhaps that is a good thing. Making good, repeatable, meaningful timings where you have a clear interpretation of the results is non-trivial, learned skill. Cross-

[issue18588] timeit examples should be consistent

Mark Lawrence added the comment: @Steven you're into timeit, do you have anything to add here? -- nosy: +BreamoreBoy, steven.daprano ___ Python tracker ___ __

[issue18588] timeit examples should be consistent

Clay McClure added the comment: There's a 68% difference in running time between the command-line and programmatic invocations shown in the current documentation, and a 1% difference between the runtimes shown in the patch. I can't speak for why that is the case, but I did find it somewhat con

[issue18588] timeit examples should be consistent

Serhiy Storchaka added the comment: In command-line invocation the gc is disabled. And timit.repeat() is used instead of timit.timit(). -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue18588] timeit examples should be consistent

Ezio Melotti added the comment: IIRC those were the actual values I got. I think I investigated why they were different, but right now I don't remember if I found out why. -- assignee: docs@python -> ezio.melotti nosy: +ezio.melotti versions: -Python 2.6, Python 3.1, Python 3.2, Pytho

[issue18588] timeit examples should be consistent

New submission from Clay McClure: The timeit module documentation includes examples of command-line and programmatic invocation, but the results between the two sets of examples don't agree. This patch brings the results into agreement with each other. -- keywords: +patch Added file:

[issue18588] timeit examples should be consistent

Changes by Clay McClure : -- assignee: docs@python components: Documentation nosy: claymation, docs@python priority: normal severity: normal status: open title: timeit examples should be consistent type: enhancement versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Py