New submission from Berker Peksag:
I noticed this while triaging issue 9317. Using traceme.py from that issue,
$ ./python -m trace -c -s traceme.py
returns nothing. It seems like it's a regression caused by
https://github.com/python/cpython/commit/17e5da46a733a1a05072a277bc81ffa885f0c204
With trace_cli_summary.diff applied:
$ ./python -m trace -c -s traceme.py
lines cov% module (path)
1 100% trace (/home/berker/projects/cpython/default/Lib/trace.py)
6 100% traceme (traceme.py)
trace_cli_summary.diff also fixes issue 10541.
----------
components: Library (Lib)
files: trace_cli_cummary.diff
keywords: patch
messages: 263921
nosy: belopolsky, berker.peksag
priority: normal
severity: normal
stage: patch review
status: open
title: trace CLI doesn't respect -s option
type: behavior
versions: Python 3.5, Python 3.6
Added file: http://bugs.python.org/file42556/trace_cli_cummary.diff
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26818>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
