-
-
Notifications
You must be signed in to change notification settings - Fork 0
Migrate to tox-dev and v4 support #34
Comments
Yes I'd be happy to move under the tox-dev organization. This plugin is very small, so a good test bed. (I find it a bit surprising the functionality isn't even built-in.) I've added testing of the plugin against tox 4 in #35 and it works perfectly. I also checked with a mini project locally and that worked fine. mini project
|
Currently, tox_configure is not called at all in v4. If it works then it must work out of the box 🤔 For what's worth I'm not against adding this functionality to the core though in v4. |
Right you are. I made a mistake in #35 and tox 3 was still being installed. I have fixed that now in #36. Getting a way to do this in tox core would be great. I have a few suggestions for how it could be added:
|
It could be though mutually exclusive with a
If |
I mean if one runs This would fit my use case of launching one CI run per Python version. My fear with the current behaviour of |
That feels something we could do 👍 |
Done via tox-dev/tox#2206 |
Thanks to that change, this plugin won't support tox 4. Instead users will be encouraged to use |
Python Version
No response
Package Version
No response
Description
Hello, would you consider moving the project under the tox-dev umbrella? See documentation under https://tox.readthedocs.io/en/rewrite/plugins.html#adoption-of-a-plugin-under-tox-dev-github-organization
Furthermore, tox v4 is getting ready and we'd like to make sure this plugin is supported from day 1, we're collecting feature gaps for this under tox-dev/tox#1974. Would be great if you could join our development chat under https://discord.gg/tox so we can assist with this. If you do so please drop in a line in the
#plugin
chat with the name of the repository you maintain. Thanks!The text was updated successfully, but these errors were encountered: