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 rhettinger
Recipients BreamoreBoy, claymation, docs@python, ezio.melotti, rhettinger, serhiy.storchaka, steven.daprano
Date 2014-06-19.20:19:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403209189.22.0.954241795.issue18588@psf.upfronthosting.co.za>
In-reply-to
Content
> 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-checking results and explaining differences are fundamental skills.  There is really no reason the docs should try to make it look easier that it really is (running the tool is easy, but interpreting results sometimes isn't).

> Being a somewhat pedantic and trivial patch, I'm fine if you 
> want to close it wontfix.

That is reasonable.  I don't that this has caused any actual impediment to learning how to use timeit.  The docs have been somewhat successful in that regard.
History
Date User Action Args
2014-06-19 20:19:49rhettingersetrecipients: + rhettinger, ezio.melotti, steven.daprano, claymation, docs@python, BreamoreBoy, serhiy.storchaka
2014-06-19 20:19:49rhettingersetmessageid: <1403209189.22.0.954241795.issue18588@psf.upfronthosting.co.za>
2014-06-19 20:19:49rhettingerlinkissue18588 messages
2014-06-19 20:19:48rhettingercreate