-
Notifications
You must be signed in to change notification settings - Fork 135
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
Support configuring through pyproject.toml #452
Comments
I need to look at the TOML spec again, but I think it should be pretty reasonably possible to put the contents of I'd be happy to review a PR adding support. (I'm unlikely to work on this myself unless there's an indication of general demand.) |
It’s more of a “it’s the correct way to do it” thing, i.e. examples should be updated and the old way should be deprecated. I’m not using nose2, I’m just maintaining a list of projects that have support already. |
Gotcha. In that case, thanks for being a good citizen and flagging this for me. 👍 Since nose2 is a "maintenance first" project at this stage in its life, I just try to set clear expectations on these things. |
Definitely want to see this happen. |
v0.15.0 is now available, with support for reading config from Please open issues if you see any problems with the new version! |
The
tool
table section of PEP 518 says that tools should store their name in[tool.<pypiname>]
inpyproject.toml
.The text was updated successfully, but these errors were encountered: