[Python-Dev] What should we do with cProfile? (original) (raw)
Alexandre Vassalotti avassalotti at gmail.com
Tue May 29 11:19:20 CEST 2012
- Previous message: [Python-Dev] [Python-checkins] cpython: Issue 14814: Add namespaces keyword arg to find(*) methods in _elementtree.
- Next message: [Python-Dev] What should we do with cProfile?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
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.
Cheers!
http://bugs.python.org/issue2919 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120529/da45dc33/attachment.html>
- Previous message: [Python-Dev] [Python-checkins] cpython: Issue 14814: Add namespaces keyword arg to find(*) methods in _elementtree.
- Next message: [Python-Dev] What should we do with cProfile?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]