Hi Ben
IIRC "testsuite: autopkgtest-pkg-pybuild" cannot handle doctests
automagically, so you probably need a custom test setup.
That's a disappointment; I hope that can be rectified in a general way
for all Debian Python packages that have Doctests to run. But for now,
yes I agree that a custom AutoPkgTest suite is the most direct way to
get it all working.
Telling autopkgtest to run the tests against the module as installed is
enough; the following works both at build time and at autopkgtest time:
export PYBUILD_TEST_ARGS = --pyargs jaraco.logging
If you're polishing things in there, there are some left-overs from your
previous attempts:
- PYBUILD_AFTER_TEST is unnecessary now that you don't have the manual
d/*install step, so you can lose a few lines from d/rules.
- PYBUILD_SYSTEM is unneeded because that is explicitly what the build
dependency on pybuild-plugin-pyproject asks for already.
- PYBUILD_INSTALL_ARGS is unneeded (it does nothing in pybuild's
pyproject-based workflow)
- --test-pytest is unneeded as the explicit build-dep on python3-pytest
means the same thing
- oldoldstable also satisfies the version constraint for python3-pytest,
so unless you are particularly keen on porting to some ancient LTS
(that won't have a new enough python3 for this package anyway), you
can skip that too.
Obviously none of these things are important…, but deleting things now
might save a future someone wondering why they were added or prevent
them propagating into other packages via copy+paste. It also inches us
towards declarative packaging by having much less in d/rules.
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
