Clarify modules used for pyproject.toml parsing are private#3385
Merged
Conversation
jaraco
approved these changes
Jun 17, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Now that we are stating that configurations passed via
pyproject.tomlcan be considered stable, we should also clarify that the code used to parse/expand/evaluate them are private (see #3232).In the future we might rename the entire
setuptools.configpackage tosetuptools._config.Summary of changes
For the time being, I am adding an entry to the changelog and a note on the module's docstring.
Closes
Pull Request Checklist
changelog.d/.(See documentation for details)