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 pitrou
Recipients bkabrda, chris.jerdonek, ncoghlan, nedbat, pitrou, serhiy.storchaka
Date 2012-07-30.01:06:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343610240.3388.29.camel@localhost.localdomain>
In-reply-to <>
Le lundi 30 juillet 2012 à 00:55 +0000, Nick Coghlan a écrit :
> However, the -C option doesn't cover the case of *implicit* invocation
> of subprocesses. This is where the PYTHONRUNFIRST suggestion comes in
> - the idea would that, unless -E is specified, then -C $PYTHONRUNFIRST
> would be implied.
> To be honest, I *don't* think this latter capability should be built
> into the core implementation. Instead, I think it is more appropriate
> for it to be handled at a virtual environment level, so that it
> doesn't inadvertently affect invocation of other applications (like
> hg) that merely happen to be written in Python.

Well, it shouldn't if you don't start doing "export PYTHONRUNFIRST=...",
but instead set it from the calling Python process (possibly from
coverage itself).

Having to create virtual environments and whatnot just to enjoy this
feature sounds terribly tedious.
Date User Action Args
2012-07-30 01:06:20pitrousetrecipients: + pitrou, ncoghlan, nedbat, chris.jerdonek, serhiy.storchaka, bkabrda
2012-07-30 01:06:19pitroulinkissue14803 messages
2012-07-30 01:06:19pitroucreate