Include tests is poetry's sdist

[jayvdb]

I am starting the process of packaging poetry for openSUSE here, and notice that the sdist doesnt contain tests, and the GitHub archive doesnt contain setup.py . As a result, there is no single versioned tarball which can be used to build and test poetry. I need to unpack both to have a usable poetry for building a testable rpm.

The easiest way to solve this is to include the tests in the poetry sdist.

[eli-schwartz]

I have just run into the same issue on Arch Linux, and this makes it difficult to package any software released using poetry (including poetry itself, and its dependencies that are also authored by @sdispater).

[eli-schwartz]

@jayvdb By the way, are you aware of the similar packaging issue in #866?

[jayvdb]

I wasn't aware of it. Thanks for the heads-up. Anyone looking to workaround some of these packaging problems with pyproject.toml projects , I found @dephell to work quite well, and the maintainer is very responsive .

[eli-schwartz]

Odd coincidence -- I'm actually attempting to package dephell as of yesterday. :p
Once that is done I am going to check out how feasible it is to add build-depends on python-dephell for poetry projects, and use dephell convert on the github sources (with testsuite) to generate a setup.py.

[sdispater]

I plan on making the packages section of the pyproject.toml file support specifying the format for which the package should be included (no format meaning all of them).

[tool.poetry]
# ...
packages = [
    { include = "my_package" },
    { include = "tests", format = "sdist" },
]

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Closing this issue automatically because it has not had any activity since it has been marked as stale. If you think it is still relevant and should be addressed, feel free to open a new one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.