[Python-Dev] What should we do with cProfile? (original) (raw)

Eli Bendersky eliben at gmail.com
Wed May 30 05:01:17 CEST 2012

As per PEP 3108, we were supposed to merge profile/cProfile into one unified module. I initially championed the change, but other things got in the way and I have never got to the point of a useful patch. I posted some code and outlined an approach how the merge could be done. However, there still a lot of details to be worked out.

So I wondering whether we should abandon the change all together or attempt it for the next release. Personally, I slightly leaning on the former option since the two modules are actually fairly different underneath even though they are used similarly. And also, because it is getting late to make such backward incompatible changes. I am willing to volunteer to push the change though if it is still desired by the community. I don't have a strong opinion either way, but if it was worth merging them for 3.3, then it's worth merging them for 3.4. Don't let "I won't be finished in time for 3.3" stop you.

+1 IMHO merging modules with their C accelerators is a worthy goal, because having two modules in the stdlib doing the same is confusing. At worst, the merged module can do everything it can in C and defer the things it can't do to Python (or defer everything on platforms where the C extension can't be built for some reason).

And as Steven said, the 3.3 timeline doesn't have anything really special about it. Although there's still time until the beta release, even if this is done for 3.4 it will be great.

Eli

More information about the Python-Dev mailing list