Should sdists include docs and tests?

[CAM-Gerlach]

@sinoroc

Correction, it says:

anything that looks like a test script: test/test*.py (currently, the Distutils don’t do anything with test scripts except include them in source distributions, but in the future there will be a standard for testing Python module distributions)

Gotcha, thanks. I wouldn’t rely on this, though, since that’s an implicit default, distutils is deprecated, things with Setuptools may have changed, and in particular are likely to much further with

Help testing experimental features in setuptools

Hello all. For the past months we have been experimenting with adding some features to setuptools, specially the support for project metadata in pyproject.toml (initially introduced in PEP 621). Other features complement it: automatic layout discovery (for flat, src or single-module layouts), defaulting to include_package_data=True, etc… The idea is to make the [tool.setuptools] table in pyproject.toml not necessary that for the simple use cases. If anyone is interested in helping testing the…

(perhaps @abravalheri might have further comments on this)

@sinoroc

Thanks. I did not know that. Interesting. I wonder if any tool actually recognizes those extras and handles them in any specific way.

Perhaps the legacy, deprecated/removed distutils commands for running tests and building docs automatically install them, but other than that I’m not aware of other tools doing so. Poetry has something like that, but AFAIK that uses their own tool config. There’s also currently plans to propose a standard PEP 517-like hook for invoking such, but it hasn’t reached the PEP stage yet.

@blink1073

No, but the regro-cf-autotick-bot uses PyPI releases to trigger automatic update PRs.

Right. Does it only work with a url source set to PyPI in the recipe, or does it work with GitHub tar sources as well? I couldn’t find any answer in the docs about that.