Log message:
py-project-metadata: updated to 0.8.0

0.8.0 (17-04-2024)

- Support specifying the ``metadata_version`` as 2.1, 2.2, or 2.3
- Always normalize extras following PEP 685
- Preserve the user-specified name style in the metadata. ``.canonical_name`` \ 
added to get the normalized name
- Require "version" in the dynamic table if unset (following PEP 621)
- Support extras using markers containing "or"
- Support empty extras
- Using ``.as_rfc822()`` no longer modifies the metadata object
- Fix email-author listing for names containing commas
- Separate core metadata keywords with commas, following the (modified) spec
- An error message reported ``project.license`` instead of ``project.readme``
- Produce slightly cleaner tracebacks
  Fix a typo in an exception message
- Subclasses now type check correctly
- The build backend is now ``flit-core``

Log message:
python/wheel.mk: simplify a lot, and switch to 'installer' for installation

This follows the recommended bootstrap method (flit_core, build, installer).

However, installer installs different files than pip, so update PLISTs
for all packages using wheel.mk and bump their PKGREVISIONs.

Log message:
py-project-metadata: add python to CATEGORIES

Log message:
py-project-metadata: not for Python 2

Log message:
devel/py-project-metadata: import py-project-metadata-0.7.1

Dataclass for PEP 621 metadata with support for [core metadata]
generation

This project does not implement the parsing of `pyproject.toml`
containing PEP 621 metadata.

Instead, given a Python data structure representing PEP 621 metadata
(already parsed), it will validate this input and generate a PEP
643-compliant metadata file (e.g. `PKG-INFO`).