-
-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-68272: add sub-millisecond display in pstats #3931
Conversation
When running pstats with functions that take less than 0.5 millisecond (per call for example), the value shown is '0.000, which isn't really helpful. This patch aims to show the value in microseconds instead of seconds for values that would otherwise be displayed as '0.000'
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. Thanks again to your contribution and we look forward to looking at it! |
(Note that I have only tested this patch against the 3.6 branch, as I can't currently compile the master branch on my development machine) |
(added my github account to my bpo account just now) |
Any update here? Would make pstats a bit more useful... |
This PR is stale because it has been open for 30 days with no activity. |
The following commit authors need to sign the Contributor License Agreement: |
This PR is stale because it has been open for 30 days with no activity. |
Closing as per #68272 (comment). |
When running pstats with functions that take less than 0.5 millisecond
(per call for example), the value shown is '0.000, which isn't really
helpful.
This patch aims to show the value in microseconds instead of seconds for
values that would otherwise be displayed as '0.000'
https://bugs.python.org/issue24084