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 nedbat
Recipients bkabrda, ncoghlan, nedbat, pitrou, serhiy.storchaka
Date 2012-07-29.13:04:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I'm -0.5 myself, though, for the reason that it complicates the startup
> process a little bit more, without looking very compelling. It smells
> disturbingly like LD_PRELOAD to me.

Antoine, do you have a suggestion for how to solve the problem?  To re-iterate: imagine you have a large test suite, and it spawns python processes during the tests.  Mercurial, for example, is like this.  You want to measure the coverage of your test suite.  This means not do you have to invoke the main suite with "python run" instead of "python", but all the subprocess invocations need to invoke as well.

We are looking for ways to make this as transparent as possible to the tests themselves, just as coverage measurement is now for test suites that don't spawn python subprocesses. describes the two current hacks people can use to invoke coverage on subprocesses.  I was hoping for a cleaner more natural solution.
Date User Action Args
2012-07-29 13:04:42nedbatsetrecipients: + nedbat, ncoghlan, pitrou, serhiy.storchaka, bkabrda
2012-07-29 13:04:42nedbatsetmessageid: <>
2012-07-29 13:04:41nedbatlinkissue14803 messages
2012-07-29 13:04:41nedbatcreate