Skip to content
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

Allow passing config settings on individual hook basis #632

Closed
wants to merge 1 commit into from

Conversation

layday
Copy link
Member

@layday layday commented Jul 1, 2023

Alternative to the flag/env var being discussed to accommodate setuptools. This would enable uses such as
-Cget_requires_for_build_wheel:--tag-build=123 -Cbuild_wheel:--compression=stored possible.

Whether per-hook configuration is desirable remains to be decided, but I thought it was an idea worth exploring.

@layday
Copy link
Member Author

layday commented Jul 1, 2023

Not able to reliably catch the invalid hook warning with pytest.warns because of:

warnings.showwarning = _showwarning

Alternative to the flag/env var being discussed to accommodate
setuptools.  This would enable uses such as
`-Cget_requires_for_build_wheel:--tag-build=123 -Cbuild_wheel:--compression=stored`
possible.
@layday layday force-pushed the feat-config-settings-per-hook branch from 4df3452 to 0ded9fc Compare July 1, 2023 14:44
@henryiii henryiii closed this Jul 29, 2023
@layday layday deleted the feat-config-settings-per-hook branch March 1, 2024 18:42
@layday layday restored the feat-config-settings-per-hook branch March 1, 2024 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants