You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a fan of poetry, and I'd potentially like to use it for packaging this library if possible.
@jayvdb My main hesitation with this is what you mentioned in #221, regarding poetry making it inconvenient to run tests for downstream packaging. Have you found any good solutions (or compromises) for this in any of the other projects you've worked with?
The text was updated successfully, but these errors were encountered:
Perhaps use poetry for everything except create the sdist with another tool which includes the tests? Previously I have used @dephell for that, but it is abandoned.
After doing a bit more digging, I think we can make this work by using the include option (roughly equivalent to MANIFEST.in, if I understand correctly) instead of packages. Also, the per-format packages support added in python-poetry/poetry#1133 appears to also apply to include, although I don't see that in the docs yet.
Example:
include = [
{ path = "tests", format = "sdist" }
]
I'm a fan of poetry, and I'd potentially like to use it for packaging this library if possible.
@jayvdb My main hesitation with this is what you mentioned in #221, regarding poetry making it inconvenient to run tests for downstream packaging. Have you found any good solutions (or compromises) for this in any of the other projects you've worked with?
The text was updated successfully, but these errors were encountered: