This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | berker.peksag |
|---|---|
| Recipients | belopolsky, berker.peksag |
| Date | 2016年04月21日.14:28:39 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1461248919.65.0.631004346458.issue26818@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016年04月21日 14:28:39 | berker.peksag | set | recipients: + berker.peksag, belopolsky |
| 2016年04月21日 14:28:39 | berker.peksag | set | messageid: <1461248919.65.0.631004346458.issue26818@psf.upfronthosting.co.za> |
| 2016年04月21日 14:28:39 | berker.peksag | link | issue26818 messages |
| 2016年04月21日 14:28:39 | berker.peksag | create | |