Stuart Prescott <[email protected]> writes: > I wish there was a PEP-standardised interface to building docs and > running tests.
Here I feel the pain less with documentation build systems, and far more with test suites. The popularity of arbitrary ‘environments” in Tox (and I assume this also applies to Nox) has led many upstream developers to cram endless dependency-laden development tasks into that, such that “just run the test suite please” is effectively impossible without installing all the upstream developer's preferred suite of helpers that have nothing to do with the test suite. To the point where developers will only run their test suite with Tox, and are not inclined to support ‘python3 -m pytest’ or the like; if they've tweaked their Tox configuration such that plain PyTest or Unittest doesn't work any more, they don't feel moved to correct that. Not to mention that many upstream test suites assume they're running from the source, not on the built and installed package. So they can't be used unmodified for AutoPkgTest. I'm neutral on whether it's achieved via a PEP, but certainly I want more enthusiastic promotion and adherence upstream to the requirements of reproducible builds and continuous integration. We need it to become typical to have a test suite that runs *without* any of the development environment assumptions. -- \ “I was in the grocery store. I saw a sign that said ‘pet | `\ supplies’. So I did. Then I went outside and saw a sign that | _o__) said ‘compact cars’.” —Steven Wright | Ben Finney
