New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coveralls-python maintenance status #393
Comments
Note: coveralls is an abandonware now, hasn't been touched for a couple of years: TheKevJames/coveralls-python#393 There is a problem when running GH workflows with coveralls==3.2.0 with having pyproject.toml as main configuration file for coverage: `ImportError: cannot import name 'FnmatchMatcher' from 'coverage.files'` Thats's why I fixed GH workflow to use latest coveralls==3.3.1 Signed-off-by: Michal Šoltis <msoltis@redhat.com>
Note: coveralls is an abandonware now, hasn't been touched for a couple of years: TheKevJames/coveralls-python#393 There is a problem when running GH workflows with coveralls==3.2.0 with having pyproject.toml as main configuration file for coverage: `ImportError: cannot import name 'FnmatchMatcher' from 'coverage.files'` Thats's why I fixed GH workflow to use latest coveralls==3.3.1 Signed-off-by: Michal Šoltis <msoltis@redhat.com>
Note: coveralls is an abandonware now, hasn't been touched for a couple of years: TheKevJames/coveralls-python#393 There is a problem when running GH workflows with coveralls==3.2.0 with having pyproject.toml as main configuration file for coverage: `ImportError: cannot import name 'FnmatchMatcher' from 'coverage.files'` Thats's why I fixed GH workflow to use latest coveralls==3.3.1 Signed-off-by: Michal Šoltis <msoltis@redhat.com>
Hey all, maintainer here. This project ended up going unmaintained for a few years, mostly because between try to balance the competing priorities of supporting the latest In an effort to avoid getting hit by that issue again, I am coming down hard in favour of not supporting any end-of-life'd pythons, not supporting >5 year old (exact cutoff tbd) coverage versions, etc. Over the coming weeks, I'll aim to get everything cleaned up accordingly. |
I'm very much in favor of only supporting versions of python that are still actively supported upstream. Folks that are sticking to older versions of python are taking security risks due to the lack of security fixes and should upgrade when possible. Python 3.8 has much improved type annotation support which, combined with mypy, significantly improves bug detection. I recommend that you look at pyupgrade as it is a great tool to help update existing code to newer python syntax with little work. We use pyugrade through gray, to auto format our codebase. |
@sodul thanks for the recommendation! I am indeed a fan of pyupgrade and have bumped it up to |
with all due respect, this is FUD |
There seems to be little activity on the project in recent years with issues that are not being directly addressed such as #373. If the project is no longer being actively maintained should it be updated to reflect that?
The text was updated successfully, but these errors were encountered: