On Sun, Jul 11, 2010 at 23:11 +1000, meme dough wrote: > Hi, > > How would disable the coverage plugin? It has setuptools entry point, > disable in coverage? Or pytest? Or patch coverage source?
By telling Ned to not include it / disable it. This way we/you are more free to advance things without depending on coverage releases. Eventually i'd like to be able to point people to a single approach for using coverage with py.test. If i understand it correctly, James and you are both working with pytest-cov now, right? best, holger > The big problem atm is just that it got out of sync with other code so > pytest crashed since it's trying to get cover_actions which didn't > exist. > > It has a lot of help output atm but indications they will be cut down. > > pytest-coverage probably need update to diff prefix maybe --coverage, > last time i checked it was hidden by coverage plugin. > > :) > > On 11 July 2010 22:46, holger krekel <hol...@merlinux.eu> wrote: > > Hi Meme, > > > > thanks for the great write up! > > Eager to try it out :) > > > > do you think it makes sense to disable coverage's own py.test - plugin? > > > > cheers, > > holger > > > > On Sun, Jul 11, 2010 at 16:40 +1000, meme dough wrote: > >> I've been looking at reworking pytest-cov a bit. > >> > >> The cmd line options are just down to 3 with .coveragerc file used to > >> control rest. > >> > >> For dist=each mode just combine and do one report since people > >> indicate that's desirable. > >> > >> Also added collecting sub process coverage as well. Provided that env > >> vars make it to the sub process then it's coverage will get measured. > >> It also works straight out of the box. > >> > >> It uses the up coming coverage 3.4 which has new api to specify source > >> roots so it won't be released until after coverage released, but I'm > >> not in hurry myself. > >> > >> In case anyone is interested you can try out the 1.0a1 with something > >> like this to get sandbox area to play with: > >> > >> cd /tmp > >> virtualenv --distribute --no-site-packages e1 > >> source e1/bin/activate > >> wget http://bitbucket.org/memedough/coverage.py/get/1a09065be67b.tar.gz > >> tar xvzf 1a09065be67b.tar.gz > >> cd coverage.py > >> python setup.py install > >> cd /tmp > >> wget http://bitbucket.org/memedough/pytest-cov/get/9cc5f8c43fd8.tar.gz > >> tar xvzf 9cc5f8c43fd8.tar.gz > >> cd pytest-cov > >> python setup.py install > >> > >> Note that I have a temp fork of coverage just to fix it's own pytest > >> plugin that causes pytest to crash. So I will delete that once > >> upstream fixed. > >> > >> :) > >> _______________________________________________ > >> py-dev mailing list > >> py-dev@codespeak.net > >> http://codespeak.net/mailman/listinfo/py-dev > >> > > > > -- > > > _______________________________________________ > py-dev mailing list > py-dev@codespeak.net > http://codespeak.net/mailman/listinfo/py-dev > -- _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
