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
Ability to include/extend other inis in tox.ini #364
Comments
configuration inclusion and inheritance are both topics that are fundamentally hard to do well/right as such we happily accept documentation showing how people would expect it to work (factors came in that way) |
zc.buildout is also based on |
I think the direction now is to move to |
closing, tox plugins should provide what was proposed |
I'm not up to date here... How does a pyproject.toml eliminate the need for a .tox?
|
Much like @Aricg, I came to this issue looking for a better description of how to do this because my group is trying to avoid having to check in, install, and subsequently maintain hundreds of tox.ini files as part of the development in our project, or create Makefile or setup.py snippets that effectively template the tox.ini files. @obestwalter, @asottile, @gaborbernat: can you please provide more details about how pyproject.toml can solve this deficiency? flake8, for instance, has the ability to append a configuration on-demand, as noted here:
|
I believe the idea above is to write a tox plugin which provides the defaults that you need. Installing a plugin which sets the reasonable defaults for your organization would remove most-if-not-all of the boilerplate of a configuration I believe the |
it would be useful to be able to share/reuse config (for example, a style toxenv) through some sort of include syntax in tox.ini.
e.g. in tox.ini:
and style.ini:
That's almost definitely not the right syntax to use, but I think it gets the idea.
The text was updated successfully, but these errors were encountered: