-
Notifications
You must be signed in to change notification settings - Fork 47
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
PEP 541 Request: pytest-flake8 #2587
Comments
@jaraco any progress so far? |
I'd like to bump this issue,
Now that we are past the 18.03.2023, pytest-flake8 fulfills all constraints to be considered abondoned. Notice that the author still didn't answer any of the tickets reaching out to him. |
This issue is even more important now that |
We are working to contact the owner to determine if they're reachable. Disclaimer: We are providing support to the PyPI Administrators to validate |
We could not reach the owner, and we consider the project abandoned per |
|
Project to be claimed
pytest-flake8
: https://pypi.org/project/pytest-flake8Your PyPI username
jaraco
: https://pypi.org/user/jaracoReasons for the request
This issue is a renewal of #1584. Although @tholo stepped up about a year ago and got a release out with some fixes, the project has gone stale again and is accumulating more and more cruft as flake8 evolves and adapts but pytest-flake8 requires workarounds to simply operate.
In tholo/pytest-flake8#91, I've reached out to offer assistance, but without response. Best I can tell, the project has been idle since Mar 2022.
Several people are interested in helping out with maintenance and I'm eager to revive the project, mentor a larger team, and get some fixes released. I'm also willing to hand the project back or give tholo control or follow his direction as he sees fit.
Maintenance or replacement?
Maintenance
Source code repositories URLs
https://github.com/tholo/pytest-flake8
https://github.com/jaraco/pytest-flake8
Contact and additional research
See description above.
Code of Conduct
The text was updated successfully, but these errors were encountered: