From b01ce4b9e8e091bd02d8e6076f86693f015ad80f Mon Sep 17 00:00:00 2001 From: Grzegorz Bokota Date: Wed, 17 Sep 2025 12:47:11 +0200 Subject: [PATCH 1/3] Improve information about configuration overriding --- docs/configuration.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/configuration.md b/docs/configuration.md index b37d785f7..d959bb0a1 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -112,7 +112,8 @@ The complete set of defaults for the current version of cibuildwheel are shown b One feature specific to the configuration files is the ability to override settings based on selectors. To use, add a ``tool.cibuildwheel.overrides`` -array, and specify a ``select`` string. Then any options you set will only +array, and specify a ``select`` string. The ``select`` need to match [build identifier](options.md#build-skip), not wheel name. +Then any options you set will only apply to items that match that selector. These are applied in order, with later matches overriding earlier ones if multiple selectors match. Environment variables always override static configuration. @@ -120,9 +121,11 @@ variables always override static configuration. A few of the options below have special handling in overrides. A different `before-all` will trigger a new container to launch on Linux, and cannot be overridden on macOS or Windows. Overriding the image on linux will also -trigger new containers, one per image. Some commands are not supported; -`output-dir`, build/skip/test_skip selectors, and architectures cannot be -overridden. +trigger new containers, one per image. + +!!! note "Some commands are not supported"" + + The ``output-dir``, ``build``, ``skip``, ``test_skip`` selectors, and architectures cannot be overridden. You can specify a table of overrides in `inherit={}`, any list or table in this list will inherit from previous overrides or the main configuration. The valid From 172681f10a983baa564fd6d64847457afac8e7f7 Mon Sep 17 00:00:00 2001 From: Grzegorz Bokota Date: Wed, 17 Sep 2025 12:55:46 +0200 Subject: [PATCH 2/3] remove obsolete " --- docs/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration.md b/docs/configuration.md index d959bb0a1..7989e0438 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -123,7 +123,7 @@ A few of the options below have special handling in overrides. A different overridden on macOS or Windows. Overriding the image on linux will also trigger new containers, one per image. -!!! note "Some commands are not supported"" +!!! note "Some commands are not supported" The ``output-dir``, ``build``, ``skip``, ``test_skip`` selectors, and architectures cannot be overridden. From 4051692e6b830ae1ca2da18cb260d1291cea2bac Mon Sep 17 00:00:00 2001 From: Grzegorz Bokota Date: Sun, 21 Sep 2025 00:37:29 +0200 Subject: [PATCH 3/3] Update docs/configuration.md Co-authored-by: Joe Rickerby --- docs/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration.md b/docs/configuration.md index 7989e0438..1e83708c3 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -112,7 +112,7 @@ The complete set of defaults for the current version of cibuildwheel are shown b One feature specific to the configuration files is the ability to override settings based on selectors. To use, add a ``tool.cibuildwheel.overrides`` -array, and specify a ``select`` string. The ``select`` need to match [build identifier](options.md#build-skip), not wheel name. +array, and specify a ``select`` string, referencing the [build identifier](options.md#build-skip) (not wheel name!). Then any options you set will only apply to items that match that selector. These are applied in order, with later matches overriding earlier ones if multiple selectors match. Environment