Skip to content

Conversation

@DimitriPapadopoulos
Copy link
Collaborator

Closes #2086.

Copy link
Collaborator

@peternewman peternewman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine in principle.

This does raise one interesting question, for backwards compatibility it would be nice if tox.ini (i.e. the new one) had the lowest priority. I don't currently know how that works, given it renders fake command line data, does --foo 1 --foo 2 mean that 1 or 2 wins, or we get both?

If we don't currently have a test for that we ought to add one (I don't know if you fancy trying that, feel free to do another PR), or I'll have a go. If we do, we should extend it to check tox.ini works too.

Because tox.ini is the latest addition to configuration files, it should
have the lowest priority. List it last in the documentation, but use the
reverse order in arguments of configparser.ConfigParser.read(), as I
suspect this functions overwrites options from prior configuration files
with options from subsequent configuration files.
@DimitriPapadopoulos
Copy link
Collaborator Author

I think tox.ini will be replaced by pyproject.toml in the future. It's probably not worth pursuing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tox.ini config file

2 participants