Set a maximum version of flit_core for build requirements #211
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.
The plan for Flit 4 is to drop support for the
[tool.flit.metadata]
project description in favour of the[project]
table, which is now standardised across different tools.More generally, I advise packages to always restrict the dependency to exclude the next major version of flit_core, so that I can make breaking changes. You can see the version ranges recommendations here: https://flit.pypa.io/en/stable/pyproject_toml.html#build-system-section