➜

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 georg.brandl
Recipients Retro, alexandre.vassalotti, andrewsmedina, barry, benjamin.peterson, brett.cannon, eric.araujo, fdrake, flox, georg.brandl, gpolo, hdiogenes, henry.precheur, jhylton, jnoller, juracy@gmail.com, kbk, orivej, pitrou, quentin.gallet-gilles
Date 2010-10-26.19:27:20
SpamBayes Score 7.4276472e-06
Marked as misclassified No
Message-id <1288121241.77.0.526978697408.issue2775@psf.upfronthosting.co.za>
In-reply-to
Content 
I will have a go at the profiler situation.

I imagine the following: deprecate the cProfile module, and provide both profiler classes from the profile module -- e.g. as PythonProfile and CProfile, and provide Profile = PythonProfile.  (From cProfile.py, obviously Profile = CProfile).  A lot of the interface (module-level helpers and script entry) are near duplicated anyway.

In 3.3, the default Profile could then be reassigned to CProfile.
History
Date User Action Args
2010-10-26 19:27:21georg.brandlsetrecipients: + georg.brandl, jhylton, fdrake, barry, brett.cannon, kbk, pitrou, alexandre.vassalotti, hdiogenes, quentin.gallet-gilles, benjamin.peterson, gpolo, orivej, jnoller, andrewsmedina, juracy@gmail.com, eric.araujo, henry.precheur, Retro, flox
2010-10-26 19:27:21georg.brandlsetmessageid: <1288121241.77.0.526978697408.issue2775@psf.upfronthosting.co.za>
2010-10-26 19:27:20georg.brandllinkissue2775 messages
2010-10-26 19:27:20georg.brandlcreate