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 pprokop
Recipients BreamoreBoy, eric.araujo, ezio.melotti, michael.foord, piotr.dobrogost, pprokop, rhettinger
Date 2012-03-02.16:23:08
SpamBayes Score 2.16396e-06
Marked as misclassified No
Message-id <1330705389.01.0.846453867716.issue4080@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with Ezio, 
this feature should have an option to enable/disable.

Anyway, I use it in different way.

Since 2008, I've used this feature for performance comparision, whether some implementation changes in application code did not slow down application. Tests run after each commit. I compare execution time of particular test before and after commit.

With additional scripts, I create metrics and charts using gnuplot to visualize how execution time of each test changed during the development.
I can ensure the performance stability of the application.
History
Date User Action Args
2012-03-02 16:23:09pprokopsetrecipients: + pprokop, rhettinger, ezio.melotti, eric.araujo, michael.foord, BreamoreBoy, piotr.dobrogost
2012-03-02 16:23:09pprokopsetmessageid: <1330705389.01.0.846453867716.issue4080@psf.upfronthosting.co.za>
2012-03-02 16:23:08pprokoplinkissue4080 messages
2012-03-02 16:23:08pprokopcreate