Just released: OSMViz 4.5.0! š
An OpenStreetMap visualization toolkit for Python
š„§ Support for Python 3.14
šŖŖ Replace deprecated classifier with licence expression (PEP 639)
š Remove GitHub attestation, PyPI attestation is enough
Just released: humanize 4.12.2 š
Bugfix release, mainly fixing the spelling of licence/license so the file is properly included in the package.
Reminder how to do PEP 639 metadata: https://hugovk.dev/blog/2025/improving-licence-metadata/
Thanks all, I just made a release with these changes: --- a/pyproject.toml +++ b/pyproject.toml @@ -2,7 +2,7 @@ build-backend = "hatchling.build" requires = [ "hatch-vcs", - "hatchling", + "hatchling>=1.27", ] [project] ... license = "BSD-3-Clause" +license-files = [ "LICENSE" ] ... classifiers = [ - "License :: OSI Approved :: BSD License", "Programming Language :: Python", "Programming Language :: Python :: 3 :: Only", "Programming Language :: Python :: 3.9", And it s...
šš¦š All the pieces (that I use) are now in place for PEP 639 ("Improving License Clarity with Better Package Metadata")!
I made sure to use latest Hatchling 1.27, added `license-files = [ "LICENSE" ]`, and deleted the deprecated licence Trove classifier.
Thanks to contributors and maintainers of PyPI, packaging, Hatchling, Twine, PyPI publish GitHub Action, build-and-inspect-python-package and of course @karo for the PEP+spec!
Thanks all, I just made a release with these changes: --- a/pyproject.toml +++ b/pyproject.toml @@ -2,7 +2,7 @@ build-backend = "hatchling.build" requires = [ "hatch-vcs", - "hatchling", + "hatchling>=1.27", ] [project] ... license = "BSD-3-Clause" +license-files = [ "LICENSE" ] ... classifiers = [ - "License :: OSI Approved :: BSD License", "Programming Language :: Python", "Programming Language :: Python :: 3 :: Only", "Programming Language :: Python :: 3.9", And it s...
@hynek looks premature to implement #pep639
Not support yet
- setuptools
- twine
- gh-action-pypi-publish
According to this post
Iām not surprised, given that the PyPA recommended upload tools do not handle metadata version 2.4 correctly. I have opened a PR to make twine and thus gh-action-pypi-publish support metadata 2.4. It would be nice if someone could have a look at it Switch to packaging for parsing metadata and support metadata 2.4 by dnicolodi Ā· Pull Request #1180 Ā· pypa/twine Ā· GitHub
@pganssle Aha, I'm using Hatchling which uses SPDX identifiers:
https://hatch.pypa.io/latest/config/metadata/#license
Which points to the draft #PEP639 ā "Improving License Clarity with Better Package Metadata":
https://peps.python.org/pep-0639/
Hopefully it'll be submitted soon. š¤
Hugo van Kemenade
Hugo van Kemenade
msftcangoblowme