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 terry.reedy
Recipients belopolsky, larry, python-dev, r.david.murray, serhiy.storchaka, terry.reedy
Date 2015-05-19.18:11:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432059082.12.0.866228418107.issue24215@psf.upfronthosting.co.za>
In-reply-to
Content
My recipe worked for me, but I am not surprised that it might fail elsewhere.  Is the specific purpose of the two problemmatic test_trace test to test that trace works with unittest?  It did not seem like it to me.  If not,  test_trace could be decoupled from other tests and use a 'tracetest.py' file that defines one function to be traced.

In the meanwhile, I think you should disable the two tests in test_trace and apply the test_pprint changes, rather than hold test_pprint hostage.
History
Date User Action Args
2015-05-19 18:11:22terry.reedysetrecipients: + terry.reedy, belopolsky, larry, r.david.murray, python-dev, serhiy.storchaka
2015-05-19 18:11:22terry.reedysetmessageid: <1432059082.12.0.866228418107.issue24215@psf.upfronthosting.co.za>
2015-05-19 18:11:22terry.reedylinkissue24215 messages
2015-05-19 18:11:22terry.reedycreate