Open broeder-j opened 1 year ago
yeah, you should make your description shorter.
While poetry is currently stuck in its own poetry-specific section of pyproject.toml, the correspondence between "description" and "summary" is kept in the python standard pyproject.toml too - see https://packaging.python.org/en/latest/specifications/declaring-project-metadata/#description
Thx. I missed that and the core metadata description is set by the message body since version 2.1 and does not correspond to description in the project metadata. (https://packaging.python.org/en/latest/specifications/core-metadata/#description) So a rich description for the upload is still possible, but not within the pyproject.toml file.... to bad.
If a raised warning about the description length prior upload somewhere is not something wanted by poetry this issue can be closed. (also not a bug, but a feature request then)
Issue
The python package build successfully by poetry gets rejected from PYPI and PYPI test for having a too long summary (512 chars), a package core metadata property.
From my understanding this occurs because:
So currently I am forced by poetry to shorten my projects description, that it also fits into the core metadata summary content for PYPI, or I cannot publish the build package there, or I would have to hack the metadata afterwards.
How this might be solved to my understanding by poetry:
Output
The same goes for