On Tue, Aug 03, 2010 at 22:43 +1000, meme dough wrote: > Hi, > > > If i understand correctly you are describing the situation as is. > > Sorry, i didn't look at the content of cov_core_init.py which would > > have revealed the mechanics that you describe. > > Yes, that's how it is now. Not expecting you to dig into the code - > just easier for me to paste it in rather than type it again :) > > > I guess somehow "pip" should be better able to uninstall. But ok, > > cov_core_init.py is hopefully not causing trouble so it's not so bad. > > python setup.py install (have to manually remove) > easy_install (have to manually remove) > pip (if distutils / distutils2 / setuptools / distribute / pip could > install and uninstall a pth file that would be great but I haven't > seen way yet)
Maybe you can change the IMPORTANT note to mention that the "cov-core" package is installing this init_cov_core.pth file so that people do not unneccessarily suspect the innocent pytest-cov plugin :) > >> --junitxml=path > >> --ignore=path > >> --genscript=path > > > > these are all file system paths. > > That is what it will be, but I can look at clarify it now. great. maybe just adapt the help string to "measure coverage for fs/import path (multi-allowed)" or so. > > This remains then the only issue i guess: rather give information > > that the specified "--cov=XYZ" restriction was used and turn up > > *no* results (even if coverage defaults disagree). Seeing everything > > is almost never what wants to see if "--cov=MORF" was specified. > > Do you agree and see a way to implement this within pytest-cov? > > That's interesting, I hadn't thought of it. Should be able to do it > though I will look. > > > Another minor note: when using --cov-report=html no information > > is printed at all. Like the junitxml or figleaf plugin i suggest > > to print the location of the generated html directory or directly > > the index.html file. > > That output could be useful and won't hurt if under continuous > integration. I will look to see if possible to get the file path > easily (could always get from config file or default but if can get > from coverage better). I think there even is some standard coverage reporting format that e.g. Hudson can read. Or it can at least grab the generated HTML. Never looked into it but would probably would be cool to have such reports available with CI runs :) best, holger _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
