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 chris.jerdonek
Recipients bkabrda, chris.jerdonek, ncoghlan, nedbat, pitrou, serhiy.storchaka
Date 2012-07-29.14:19:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ned, two questions: in the scenario you just described, is it a requirement that your test suite's code need not be modified (even minimally) to support coverage of subprocesses?

And can the solution assume that the test suite is spawning the Python processes in certain standard ways, or must it address all possible ways (even convoluted ones)?  If the former, what are the standard ways?  I am referring to things like the path to the Python interpreter invoked and how that is obtained, whether the subprocess module is always used, etc.

These questions are meant to help pin down the scope of what needs to be satisfied.
Date User Action Args
2012-07-29 14:19:15chris.jerdoneksetrecipients: + chris.jerdonek, ncoghlan, pitrou, nedbat, serhiy.storchaka, bkabrda
2012-07-29 14:19:15chris.jerdoneksetmessageid: <>
2012-07-29 14:19:14chris.jerdoneklinkissue14803 messages
2012-07-29 14:19:14chris.jerdonekcreate