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
Is this plugin maintained? #30
Comments
That's because this repo was created against the alpha release of tox and supports only v4 from get go. Do you have a repro? PR to fix it is welcomed. |
The linked config files and GH Actions output in the initial comment show my attempt to use this plugin, and the result. I don't have a more minimal reproduction than that at the moment. |
I am more than happy to review a PR for this one |
I understand that part. But it seems like there's been no real activity in the repository for a long time, no new releases that might indicate compatibility with the 4.0 |
That's because I've been busier with tox 4 core issues than this extension. If someone would fill in a PR I'd take a look though. I'm only one person doing it in their free time so 🤷 |
@ubernostrum By now you should know how open-source works. If my hint was not enough, let me be more explicit: if you want something to happen you better start doing it yourself (contributing) or pay someone to do it for you. |
@ssbarnea I'm not sure why the simple question -- whether or not this plugin is maintained -- warrants such a response. But don't worry, you won't have to deal with any further interactions from me. |
I notice the last release is almost a year ago, predated the actual release of
tox
4.0, and the only commits to this repository since January appear to be automated or semi-automated dependency bumps.I also notice that the plugin does not appear to work at the moment -- this GitHub Actions config and this tox config yielded a CI run that appears to have tried to run every environment on every Python version, rather than only the specified environments for each Python version.
The text was updated successfully, but these errors were encountered: