Warn if packages still using flit.buildapi instead of flit_core.buildapi #674
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'm not 100% sold on this: the removal would break things that might otherwise work, and it's a tiny bit of complexity by itself. But any project still specifying
flit.buildapi
is probably also using old-style metadata ([tool.flit.metadata]
table), which 4.0 will likely not support (#673), and that is enough complexity to be worth cleaning up.flit.buildapi
added in 0.12 (November 2017)flit_core.builadpi
added in 2.0 (November 2019)[project]
from PEP 621) added in 3.2 (March 2021)Using
python -m build
, this warning is visible. Usingpip wheel
(and presumably any other pip command that does a build), it isn't (pip wheel -v
shows it). I don't think there's anything we can do to make it more visible, but a warning that only some people see is better than no warning.First step for #519