Ned Batchelder
Ned Batchelder
@offbyone I'm not sure what you mean by an API. Coverage.py has an API. Would that work? Keeping all the code in pytest-cov but exposing it in an API from...
@meejah I am in favor of exploring the parts of pytest-cov that could be moved into coverage.py itself. To keep the process a little simpler now, I'm only talking here...
@merwok I think I like the idea of changing the name. We could make one more release of pytest-cov, where it prints a warning that there will be no more...
I suggest there's no need to add this to pytest-cov at all. Let pytest run the tests. Let coverage report on coverage. See #337.
A `-q` option would be great: I build sdist and wheels as part of my quality step, and switching from setup.py to build has exploded the output with dist-building details...
People continue to write new issues here. We could add GitHub issue and pull request templates that make clear that no action will be taken on issues or pull requests....
I definitely agree that a focus for the organization would be important. "Python web stack" sounds reasonable, as long as we recognize that all sorts of generic Python things (like...
I'm also frustrated by the "what do I get for my money?" mindset, considering how much they have already gotten. But, if we can show something tangible, we'll have an...
One thing to look at is NumFocus: http://www.numfocus.org/open-source-projects.html How do they get sponsors? Do they offer something that gets Microsoft on board?
@nayafia when you make a survey, I can help spread it around the Boston area.