-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
PEP 517 config settings support #3080
Comments
PR welcome 👍 |
In tox's output, I see that
I suppose this comes from pyproject-api. I can't quite see right now how this is called. Edit: This |
I've found where |
https://tox.wiki/en/4.6.4/plugins.html#tox.plugin.spec.tox_add_env_config, you should have plenty examples in the code base, check for example https://tox.wiki/en/4.6.4/config.html#package_root-env |
I'm trying to mimick what's in #1891, but don't really know what I'm doing. I'll best open a PR so we can discuss further over there. |
Done. |
In #573, support for PEP 517 was added. From what I can tell, config settings support is still missing. Config settings are a dict that is passed to the build backend, e.g., setuptools. Pip implements this as
--config-settings
/-C
, pypa-build as--config-setting
/-C
.It'd be great if tox had some way of specifying config settings that a passed to the build backend, e.g.,
The text was updated successfully, but these errors were encountered: