Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Switch build-backend to flit_core + use License-Expression for project metadata #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 4 commits into from
Mar 29, 2025
Merged

Switch build-backend to flit_core + use License-Expression for project metadata #59

merged 4 commits into from
Mar 29, 2025

Conversation

cdce8p
Copy link
Contributor

@cdce8p cdce8p commented Mar 28, 2025 •
edited
Loading

Setuptools v77 added support for SPDX license expressions with the "new" syntax for project.license. Unfortunately, the setuptools version no longer supports Python 3.8, so we would need to drop it here as well if we want to use the new syntax.
Switch build-backend to flit-core for PEP 639 license expression support.

Metadata diff

 ...
-License: MIT
+License-Expression: MIT
 ...
-Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.8
 ...

This is a followup to #53.

hauntsaninja
hauntsaninja reviewed Mar 28, 2025
View reviewed changes
Copy link
Collaborator

@hauntsaninja hauntsaninja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could switch to flit_core or something?

(Could also be nice to avoid forcing very recent lower bounds on setuptools given their approach towards backcompat and PIP_CONSTRAINT is not a flexible hammer)

@cdce8p cdce8p changed the title Use License-Expression for project metadata + drop Python 3.8 Switch build-backend to flit_core + use License-Expression for project metadata Mar 28, 2025
@cdce8p
Copy link
Contributor Author

cdce8p commented Mar 28, 2025

(Could also be nice to avoid forcing very recent lower bounds on setuptools given their approach towards backcompat ...)

Flit_core also added basic support for it only recently with 3.11.

Maybe we could switch to flit_core or something?

The switch was actually quite seamless. At least for such a simple project. Nice to know that the ecosystem has finally reached this point it's working towards for so long.

@cdce8p cdce8p requested a review from hauntsaninja March 28, 2025 21:58
@hauntsaninja hauntsaninja merged commit 8d272bb into python:master Mar 29, 2025
7 checks passed
@cdce8p cdce8p deleted the update-setuptools branch March 29, 2025 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hauntsaninja hauntsaninja hauntsaninja approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@cdce8p @hauntsaninja