bpo-34861 Make cProfile default output more useful#9655
Conversation
ce14a9f to
4bce0c3
Compare
October 1, 2018 11:21
|
Excuse the ping here, but what can I do to move this forward? This is a very simple change that make a HUGE difference in usability, and it has been reviewed already. How can this be merged? |
Sorry, something went wrong.
pablogsal
left a comment
There was a problem hiding this comment.
Hi @boxed and thanks for the PR. I would suggest splitting this PR into the one changing the default and the one changing the path because I have some doubts regarding the path approach but I don't want to block on the default, as that is indeed a good improvement.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
I clicked on the "resolve conversation" button to let you know I've answered the questions. I hope that was the right thing to do and doesn't appear rude or something. I'm unsure what the etiquette is... |
Sorry, something went wrong.
|
Ah, I need to do this too: I have made the requested changes; please review again. I haven't made all the requested changes, but I have replied to the discussion at least. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @pablogsal: please review the changes made to this pull request. |
Sorry, something went wrong.
pablogsal
left a comment
There was a problem hiding this comment.
Check out this comment: https://github.com/python/cpython/pull/9655/files#r504605933
I kindly insist on what I said before: I think is easier to split the PR.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
I have made the requested changes; please review again. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @pablogsal: please review the changes made to this pull request. |
Sorry, something went wrong.
|
@boxed Did you forgot to push your changes? The last commit here was 3 days ago |
Sorry, something went wrong.
|
@pablogsal Yes I did :( I have pushed now and resolved a merge conflict I got now too. |
Sorry, something went wrong.
99d996d to
f13da29
Compare
October 18, 2020 11:22
|
I rebased and squashed everything, and fixed the docs. I was so far out of date with master that this was needed (due to this PR started its life in 2018). |
Sorry, something went wrong.
f13da29 to
63e8549
Compare
October 19, 2020 06:33
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
Display one folder level for pstats.stripdirs() when filename starts with __ (__init__.py, __main__.py primarily)
32bde8f to
f6da3b6
Compare
February 27, 2025 06:56
|
I have reapplied the change on top of current |
Sorry, something went wrong.
|
How do I remove the stale tag? I don't think it's correct. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
For a test script:
The old output is:
after this change the output is:
https://bugs.python.org/issue34861