Re: Autopkgtest smoke test for Python libraries

2016-03-01 Thread Ben Finney
Yaroslav Halchenko writes: > sorry if I came late to the discussion and missing the point, but > pybuild/dh-python already has some tests discovery mechanisms Have another read of the thread: this is not about running the upstream test suite. It is about making a

Re: Autopkgtest smoke test for Python libraries

2016-03-01 Thread Paul Wise
On Wed, Mar 2, 2016 at 6:53 AM, Ben Finney wrote: > Who can recommend a way to make this a more automated part of the Debian > Python package build workflow? Add things that should be changed to `cme fix` or pypi2deb https://wiki.debian.org/AutomaticPackagingTools -- bye, pabs

Re: Autopkgtest smoke test for Python libraries

2016-03-01 Thread Ben Finney
Martin Pitt writes: > Thanks to Matthias for pointing this out to me. I try to reply > in-thread. Please keep CC:ing me as I'm not subscribed. Done. > > The goal is to perform a simple “smoke test” to verify the correct > > installation of the Python libraries from the Debian

Re: Autopkgtest smoke test for Python libraries

2016-03-01 Thread Barry Warsaw
On Mar 01, 2016, at 06:10 PM, Martin Pitt wrote: >You could use it for that purpose indeed, but that's not really what >it is intended for. The idea is that the generic tests apply to all >packages of a particular type, so you can change them centrally >instead of having to modify and upload

Re: Autopkgtest smoke test for Python libraries

2016-03-01 Thread Martin Pitt
Hey Barry, Barry Warsaw [2016-03-01 10:48 -0500]: > I gather that it's supposed to be used by the maintainer in a source package > ($vcs repo) to jumpstart a debian/tests directory? You could use it for that purpose indeed, but that's not really what it is intended for. The idea is that the

Re: Autopkgtest smoke test for Python libraries

2016-03-01 Thread Barry Warsaw
On Mar 01, 2016, at 09:05 AM, Martin Pitt wrote: >Very nice! There's precedent for Perl, Ruby and DKMS packages which >have a fairly standard way to run the upstream test suite. For Python >there are some conventions, like "./setup.py test" or running >nosetests, maybe it's worth experimenting

Re: Autopkgtest smoke test for Python libraries

2016-03-01 Thread Martin Pitt
Hello all, Thanks to Matthias for pointing this out to me. I try to reply in-thread. Please keep CC:ing me as I'm not subscribed. > The goal is to perform a simple “smoke test” to verify the correct > installation of the Python libraries from the Debian packages, for all > relevant Python

Autopkgtest smoke test for Python libraries

2016-02-24 Thread Ben Finney
Howdy all, I am experimenting with Autopkgtest[0] for Python library packages. Perhaps others can use what I've made and/or make suggestions for improvement. The ‘python-lockfile’ Debian packaging VCS now has a smoke test suite