Docs: clarify how multiple values work for various options #2070
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I spent a long while wondering why comma-separated values wouldn't work for `CIBW_SKIP`.
|
I believe we put them in the tabbed box because that rule only applies to environment variables. In TOML, the options are supplied as a list of strings. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I spent a long while wondering why comma-separated values wouldn't work for
CIBW_SKIP, since this information was cleverly hidden inside the Examples box:This PR unifies that for all of the multiple-values-supported options; this was already documented in the prose for the environment variable options, so the extra repetition of the same information is now gone from the example box's footer.