search

bukzor / python-coverage-enable-subprocess

10 stars 0 forks source link

Should this be moved into coverage.py? #1

Open nedbat opened 8 years ago

nedbat commented 8 years ago

How does this relate to https://bitbucket.org/ned/coveragepy/issues/378/default-support-for-coverage_process_start ? What needs to be done to it still?

bukzor commented 8 years ago

Hi Ned!

I think this is an implementation of that feature request. I believe it's production worthy, with the caveat that it does not give subprocess support under easy-install (which includes install -e / setup.py install).

My intent was to use this myself for a bit, then port it to be a coveragepy feature branch.

On Sat, Nov 21, 2015 at 5:17 AM Ned Batchelder notifications@github.com wrote:

How does this relate to https://bitbucket.org/ned/coveragepy/issues/378/default-support-for-coverage_process_start ? What needs to be done to it still?

— Reply to this email directly or view it on GitHub https://github.com/bukzor/coverage_enable_subprocess/issues/1.

blueyed commented 5 years ago

Would be great to have this by default, i.e. in coveragepy.

with the caveat that it does not give subprocess support under easy-install (which includes install -e / setup.py install).

To be clear: this means pip install -eing coverage-enable-subprocess - it works for installing your own app in develop mode.

Is this required to be included with coveragepy (i.e. where coveragepy would be installed in develop mode), @nedbat ? (related issue #2)

ssbarnea commented 3 months ago

@nedbat WDYT about this? AFAIK, is still valid.

bukzor commented 3 months ago

FWIW: I still use it and it still works well, given the setup shown in readme.