We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After helping to complete #3090 (thanks!), one can now pass config_settings to the build backends via, e.g.,
config_settings
[testenv:.pkg] config_settings_build_sdist = A = b config_settings_build_wheel = X = y
I noticed though that when building sdists, the subsequent installation step
py3: install_package> python -I -m pip install --force-reinstall --no-deps /path/to/.tox/.tmp/package/1/foobar-1.0.0.tar.gz
again employs wheel building without the config settings being passed. They would have to be passed to to pip as --config-settings.
--config-settings
Would it be sensible to introduce another variable here, or should config_settings_build_wheel be used?
config_settings_build_wheel
The text was updated successfully, but these errors were encountered:
We don't want another variable. config_settings_build_wheel could be passed on as an env var here perhaps 🤔
Sorry, something went wrong.
Am I understanding this correctly? config_settings_build_wheel does NOT pass to install_package. is this a bug or by design?
nschloe
No branches or pull requests
After helping to complete #3090 (thanks!), one can now pass
config_settings
to the build backends via, e.g.,I noticed though that when building sdists, the subsequent installation step
again employs wheel building without the config settings being passed. They would have to be passed to to pip as
--config-settings
.Would it be sensible to introduce another variable here, or should
config_settings_build_wheel
be used?The text was updated successfully, but these errors were encountered: