Ned Batchelder
Ned Batchelder
Instead of trying to un-coverage inside pycharm, it might be easier to adjust how you are running coverage outside of pycharm. How do you run the tests outside? If you...
I guess we have a difference of philosophy. I would rather teach my collaborators to type "tox" or "make test" than to try to have everything done implicitly by "pytest".
I think I have seen race conditions between erasing the data files and writing new data. I'm working on getting more information.
/cc @ionelmc @graingert
@jezdez Is there something i can do to clear up the confusion (if that's what the emoji means!)? I may have written too fast and left out some context.
1) A few people have mentioned the convenience of having one command (pytest --cov-etc) that will run tests and produce coverage reports. I understand that convenience, but a simple shell...
@maurobaraldi I'm not sure who would maintain the enhanced one. If I only contribute to the plain version (to add support for new coverage.py features), then the enhanced won't be...
> Could it be an option make pytest-cov just a commad wrapper around coverage and do noting itself anymore? @loechel, there are important things pytest-cov does that only it can...
There were 26 +1's on the top description. I don't know how to see the names in the GitHub UI. I had to use the API to get them: blueyed,...
I hear what you are saying about dealing with the fallout. I think probably everyone is on-board with dropping support for older everything (though I would like to keep Python...