Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
allow v2.3 in metadataversion, fallback to any string (#344)
someone recently showed me an issue validating the manifest of a napari plugin, ``` ValidationError: 1 validation error for PackageMetadata metadata_version unexpected value; permitted: '1.0', '1.1', '1.2', '2.0', '2.1', '2.2' (type=value_error.const; given=2.3; permitted=('1.0', '1.1', '1.2', '2.0', '2.1', '2.2')) ``` What happened is that PEP685 https://peps.python.org/pep-0685/ added a new spec (v2.3), and some build backends have begun to implement it. For example, hatchling (which this package was using) bumped their default version to v2.3 5 days ago: pypa/hatch@1a9c30d This PR just relaxes the validation of metadata_version to allow for any string. @napari/core-devs, this is something that would be important to get in soon and push a new release. Packages that use setuptools will not have this issue, but anything using hatchling after [1.22.1](https://github.com/pypa/hatch/releases/tag/hatchling-v1.22.1) (released on Mar 15) will begin to see this
- Loading branch information