Serhiy Storchaka added the comment:
Sorry, I expected this issue be solved much faster.
Unfortunately Terry's recipe doesn't work. Here is a patch that reapplies
changes that broke buildbots (additional tests for buildins and making
test_pprint discoverable), and also fixes test_trace and makes it discoverable.
I found yet one issue with test_trace. It fails if run regrtest with the -m
option (both patched and unpatched versions, there is no regression).
$ ./python -m test.regrtest test_trace
[1/1] test_trace
1 test OK.
$ ./python -m test.regrtest -m test_coverage test_trace
[1/1] test_trace
test test_trace failed -- Traceback (most recent call last):
File "/home/serhiy/py/cpython-3.4/Lib/test/test_trace.py", line 313, in
test_coverage
self.assertTrue("pprint.cover" in files)
AssertionError: False is not true
1 test failed:
test_trace
It fails because run_unittest() is used in tested script. That is yet one
argument against using test_pprint in test_trace.
----------
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file39431/issue24215.patch
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24215>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
