Support Metadata 2.5 (PEP 794)

[edgarrmondragon]

Description

Adds support for PEP 794, which bumps core metadata to version 2.5 and introduces fields Import-Name and Import-Namespaces.

• Names are validated with str.isidentifier(), after splitting each name into its submodules, if any
• Import names starting with _ are marked as private with the ; private modifier

TODOs

Empty Import-Name

Projects MAY set import-names an empty array and not set import-namespaces at all in a pyproject.toml file (e.g. import-names = []). To match this, projects MAY have an empty Import-Name field in their metadata. This represents a project with NO import names, public or private (i.e. there are no Python modules of any kind in the distribution file).

UPDATE: b82f8ac

Handle ambiguity

If a project lists the same name in both Import-Name and Import-Namespace, then tools MUST raise an error due to ambiguity; this also applies to import-names and import-namespaces, respectively.

UPDATE: ba5812d, cabee35

Add a default Import-Name

in practice the majority of projects have their project name match what their import name would be. As such, it is a reasonable assumption to make that a project name that is normalized in some way to an import name (e.g. packaging.utils.canonicalize_name(name, validate=True).replace("-", "_")) can be used if some answer is needed.

Links

• Update the default version of core metadata to 2.4 #1790 (for "inspiration")
• https://peps.python.org/pep-0794
• https://packaging.python.org/en/latest/specifications/pyproject-toml/#import-names
• Support Core Metadata 2.5 (PEP 794, Import-Name, Import-Namespace) pypi/warehouse#19083
• metadata: initial 2.5 support pypi/warehouse#19254
• New release for PEP 794 and packaging.pylock packaging#950