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 tha
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?
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,
Fa
On 1/3/20 3:08 PM, Petr Viktorin wrote:
> The "python-sig" FAS group [3] is something slightly different. It's
> confusingly named (IIRC only groups with "-sig" in their name can get
> some permissions). It's there for people who want to fix Python-related
> issues in all the packages. Something li
