Hi all,
I see more and more projects moving to use pyproject.toml and poetry. They still are publishing tarballs at PyPI but they often miss the documentation and/or the tests.
What is the approach to deal with upstream project which are using poetry? Simply use PyPI as source?
Kind regards,
Fabian
On 07. 01. 20 19:26, Fabian Affolter wrote:
Hi all,
I see more and more projects moving to use pyproject.toml and poetry. They still are publishing tarballs at PyPI but they often miss the documentation and/or the tests.
What is the approach to deal with upstream project which are using poetry? Simply use PyPI as source?
If you intent to run the tests, I would work with upstream to include the tests to the tarball and I would fallback to a github tagged tarball in the meantime.
Hi,
I'm not used to poetry yet. Is it a flaw in poetry to skip documentation and tests by default? On my personal projects, I'm trying to ensure that the sdist contains all files of the Git repository using MANIFEST.in.
I agree with Miro that it's better to collaborate with upstream to ensure that archives published on PyPI contain tests and documentation.
Victor
Le mar. 7 janv. 2020 à 19:26, Fabian Affolter fab@fedoraproject.org a écrit :
Hi all,
I see more and more projects moving to use pyproject.toml and poetry. They still are publishing tarballs at PyPI but they often miss the documentation and/or the tests.
What is the approach to deal with upstream project which are using poetry? Simply use PyPI as source?
Kind regards,
Fabian
python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproje...
python-devel@lists.fedoraproject.org