Pyproject-metadata

Latest version: v0.8.0

Safety actively analyzes 623860 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

0.8.0

==================

- 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``

0.7.1

==================

- Relax ``pypa/packaging`` dependency

0.7.0

==================

- Use UTF-8 when opening files
- Use ``tomllib`` on Python >= 3.11

0.6.1

==================

- Avoid first and last newlines in license contents

0.6.0

==================

- Make license and readme files ``pathlib.Path`` instances
- Add the license contents to the metadata file
- Add support for multiline data in metadata fields

0.5.0

==================

- Renamed project to ``pyproject_metadata``
- Support multiple clauses in requires-python
- Error out when dynamic fields are defined
- Update dynamic field when setting version

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.