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 alexandre.vassalotti
Recipients MrJean1, alexandre.vassalotti, barry, benjamin.peterson, brett.cannon, hdiogenes
Date 2009-07-07.00:37:04
SpamBayes Score 1.971431e-06
Marked as misclassified No
Message-id <1246927027.81.0.418760035609.issue2919@psf.upfronthosting.co.za>
In-reply-to
Content
Here's an updated version of my lsprof.py module. I fixed a few bugs,
includes the awful reference leak that was present in the previous
version (i.e., the profiler code was keeping a reference to every frame
executed).

I consider the lsprof.py code functionally equivalent to _lsprof. Now, I
am wondering if I should add the features from profile.py missing in
_lsprof, e.g., the bias argument and the calibration code.
History
Date User Action Args
2009-07-07 00:37:08alexandre.vassalottisetrecipients: + alexandre.vassalotti, barry, brett.cannon, hdiogenes, MrJean1, benjamin.peterson
2009-07-07 00:37:07alexandre.vassalottisetmessageid: <1246927027.81.0.418760035609.issue2919@psf.upfronthosting.co.za>
2009-07-07 00:37:06alexandre.vassalottilinkissue2919 messages
2009-07-07 00:37:06alexandre.vassalotticreate