package published to pypi is missing project description.

[BeyondEvil]

My previous release shows the long description in pypi.

My latest release, using poetry publish, does not.

How can I fix this?

https://github.com/pytest-dev/pytest-metadata/blob/master/.github/workflows/publish.yml#L29-L34

https://github.com/pytest-dev/pytest-metadata/blob/master/setup.py

https://github.com/pytest-dev/pytest-metadata/blob/master/setup.cfg#L4-L5

[abn]

You should probably add readme = "README.rst" to your pyproject.toml file.

Additionally, best to drop both the setup.py and setup.cfg files as they are only required for setuptools. Move the metadata to the tool.poetry section.

You should probably also update your build-system section to be something like

poetry/pyproject.toml

Lines 74 to 76 in 15f6ec1

	[build-system]
	requires = ["poetry-core>=1.0.0"]
	build-backend = "poetry.core.masonry.api"

You can test all this by locally doing poetry build then checking metadata in the wheel generated.

[abn]

The setup.cfg is useless for a poetry project and it is never read at all.

The fix is to define entrypoint plugins as documented at https://python-poetry.org/docs/pyproject/#plugins

As for including the tests, us the include statement.

https://github.com/python-poetry/poetry-core/blob/213e3670b6287053b350e8c29972e0ea2e7526a5/pyproject.toml#L24-L26

[BeyondEvil]

The setup.cfg is useless for a poetry project and it is never read at all.

Even tho I define this under the build? https://github.com/pytest-dev/pytest-metadata/blob/master/pyproject.toml#L1-L8

[abn]

If you use poetry build the build-system section will be ignored. It's only used when a PEP517 frontend like pip or build is used. And if you have setuptools in there, poetry-core won't be used to build the project, but setuptools. That causes all sorts of other problems and inconsistencies. TL;DR is it needs to be as I indicated in my first comment.

[BeyondEvil]

If you use poetry build the build-system section will be ignored. It's only used when a PEP517 frontend like pip or build is used. And if you have setuptools in there, poetry-core won't be used to build the project, but setuptools. That causes all sorts of other problems and inconsistencies. TL;DR is it needs to be as I indicated in my first comment.

Ok, it's starting to make sense now. 😊

Thanks for taking the time to explain it. 🙇

[abn]

@BeyondEvil added pytest-dev/pytest-metadata#44 to make things a bit clearer. (hopefully)