[issue24084] pstats: sub-millisecond display

2019-11-22 Thread Inada Naoki
Change by Inada Naoki : -- nosy: +inada.naoki ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24084] pstats: sub-millisecond display

2018-03-09 Thread Ned Deily
Ned Deily added the comment: Based on the review comments, it looks like the existing PR 3931 needs to be revised and resubmitted against current master branch. So, can we close PR 3931? -- nosy: +ned.deily versions: +Python 3.8 -Python 3.5

[issue24084] pstats: sub-millisecond display

2017-10-12 Thread STINNER Victor
STINNER Victor added the comment: > I concur with Victor. This change likely breaks graphical viewers of pstat > data. I propose to *do* break the format by always displaying percall timings with a precision of 6 digits. --

[issue24084] pstats: sub-millisecond display

2017-10-12 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: I concur with Victor. This change likely breaks graphical viewers of pstat data. How gprof and similar tools solve the problem of outputting sub-millisecond timings? -- ___ Python

[issue24084] pstats: sub-millisecond display

2017-10-12 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- Removed message: https://bugs.python.org/msg304247 ___ Python tracker ___

[issue24084] pstats: sub-millisecond display

2017-10-12 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: I concur with Victor. This change likely breaks graphical viewers of pstat data. How gprof and similar tools solve the problem of outputting sub-microsecond timings? -- nosy: +serhiy.storchaka

[issue24084] pstats: sub-millisecond display

2017-10-09 Thread Romuald Brunet
Romuald Brunet added the comment: I figured we didn't want to change the size of the columns (+12 COL), but this could easily be done yes -- ___ Python tracker

[issue24084] pstats: sub-millisecond display

2017-10-09 Thread STINNER Victor
STINNER Victor added the comment: Hum, "2447µs" makes the output more difficult to parse (by a program) and to read (by a human). Why not always displaying 6 digits (after the dot) for the two "percall" columns. -- nosy: +haypo

[issue24084] pstats: sub-millisecond display

2017-10-09 Thread Roundup Robot
Change by Roundup Robot : -- pull_requests: +3906 ___ Python tracker ___

[issue24084] pstats: sub-millisecond display

2015-04-30 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +georg.brandl stage: - patch review versions: +Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24084 ___

[issue24084] pstats: sub-millisecond display

2015-04-30 Thread Romuald Brunet
New submission from Romuald Brunet: 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