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 r.david.murray
Recipients martin.panter, mattpr, mdk, ned.deily, paul.moore, r.david.murray, rogerwang, ronaldoussoren, steve.dower, tim.golden, v+python, zach.ware
Date 2017-12-27.13:51:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514382677.53.0.213398074469.issue31639@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think the PR as it stands is a good idea.  These classes are designed to be composable, so it should be up to the library user whether or not to use threads.  However it would be perfectly reasonable to choose to use threads in the 'test' function and thus the cli.  Which fact should then be documented, and chromium can even be mentioned as one of the motivations for using threads in the cli server.
History
Date User Action Args
2017-12-27 13:51:17r.david.murraysetrecipients: + r.david.murray, paul.moore, ronaldoussoren, tim.golden, ned.deily, v+python, martin.panter, zach.ware, steve.dower, mdk, mattpr, rogerwang
2017-12-27 13:51:17r.david.murraysetmessageid: <1514382677.53.0.213398074469.issue31639@psf.upfronthosting.co.za>
2017-12-27 13:51:17r.david.murraylinkissue31639 messages
2017-12-27 13:51:17r.david.murraycreate