build: support flit-core 4 by migrating metadata to PEP 621 - #42
Open
stanislavlevin wants to merge 1 commit into
Open
build: support flit-core 4 by migrating metadata to PEP 621#42stanislavlevin wants to merge 1 commit into
stanislavlevin wants to merge 1 commit into
Conversation
flit-core 4 removed the legacy `[tool.flit.metadata]` table:
flit_core.config.ConfigError: The [tool.flit.metadata] table is no
longer supported. Switch to the standard [project] table or require
flit_core<4 to build this package.
Move the metadata to the standard `[project]` table:
- `dist-name` -> `name`, `author` -> `authors`, `description-file` ->
`readme`, `requires` -> `dependencies`
- `module = "delinea"` -> `[tool.flit.module]`, since the module name
differs from the distribution name
- version and summary keep coming from the module's `__version__` and
docstring, now declared via `dynamic`
- the license classifier becomes the SPDX expression `Apache-2.0`
(PEP 639), which needs flit_core >= 3.12
- the project URL moves to `[project.urls]`
Require `flit_core >=3.12,<5` instead of pinning an exact version, so a
future flit-core major does not break the build again.
The built metadata is unchanged apart from `License-Expression:
Apache-2.0` replacing the license classifier.
Docs:
- https://flit.pypa.io/en/stable/history.html#version-4-0
- https://flit.pypa.io/en/stable/pyproject_toml.html#pyproject-toml-project
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Stanislav Levin <slev@altlinux.org>
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
1 participant
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.
flit-core 4 removed the legacy
[tool.flit.metadata]table:Move the metadata to the standard
[project]table:dist-name->name,author->authors,description-file->readme,requires->dependenciesmodule = "delinea"->[tool.flit.module], since the module name differs from the distribution name__version__and docstring, now declared viadynamicApache-2.0(PEP 639), which needs flit_core >= 3.12[project.urls]Require
flit_core >=3.12,<5instead of pinning an exact version, so a future flit-core major does not break the build again.The built metadata is unchanged apart from
License-Expression: Apache-2.0replacing the license classifier.Docs: