Andrey Rakhmatullin <[email protected]> writes: > I think you need to point autopkgtest to the installed file explicitly > (you either failed to mention that the only tests in the package are > doctests in the actual module or missed that fact yourself).
Thank you both; yes, I knew that Doctest expects to find and read the Python module files directly, and that AutoPkgTest expects to test the installed Python package. But I had not made the connection between them, that they are therefore in conflict. This makes sense of the test suite failure. Jeroen Ploemen <[email protected]> writes: > 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. > See jaraco.text and jaraco.context for ways to hack things into > place. Neither will win a beauty contest, but it works. Thank you, I have looked at those and adapted some other custom AutoPkgTest suites I had written. I now have a custom AutoPkgTest that looks to the installed Python modules and runs the Doctests found there. It is passing that step now. This has been helpful. Yet I am still interested to know of plans to get a general solution for AutoPkgTest to run Doctest on the installed Python modules. -- \ “I must have a prodigious quantity of mind; it takes me as much | `\ as a week sometimes to make it up.” —Mark Twain, _The Innocents | _o__) Abroad_ | Ben Finney <[email protected]>
signature.asc
Description: PGP signature
