autopkgtest'ing against multiple Python versions

2012-04-21 Thread Jakub Wilk
I started adding DEP-8 tests to my packages. It worked reasonably well so far (after I fixed #648148 localy...). However, I have doubts about which strategy to choose when it comes to testing with multiple Python versions. The following schemes come to my mind: 1) Test only with default versio

Re: autopkgtest'ing against multiple Python versions

2012-04-21 Thread Yaroslav Halchenko
Cool, Jakub, 3 (enhanced with Recommends) sounds like a perfect solution to me as well... if only someone hacked it up for autopkgtest? would you also mind pointing to the 'best of the breed' package fro which you have created an autopkgtest pkg? > (since then you do want to install python-all

Re: autopkgtest'ing against multiple Python versions

2012-04-22 Thread Jakub Wilk
* Yaroslav Halchenko , 2012-04-21, 19:24: 3 (enhanced with Recommends) sounds like a perfect solution to me as well... if only someone hacked it up for autopkgtest? I was tempted even to add Recommends now and wait patiently until it's implemented... but it turns down that I can't. The specific

Re: autopkgtest'ing against multiple Python versions

2012-04-23 Thread Jakub Wilk
* Jakub Wilk , 2012-04-22, 10:03: would you also mind pointing to the 'best of the breed' package fro which you have created an autopkgtest pkg? http://anonscm.debian.org/viewvc/python-modules/packages/gamera/trunk/debian/tests/ Maybe it was not a good example after all. :) I just realized th

Re: autopkgtest'ing against multiple Python versions

2012-04-23 Thread Yaroslav Halchenko
On Mon, 23 Apr 2012, Jakub Wilk wrote: > Maybe it was not a good example after all. :) I just realized that, > according to adt-run, the tests were failed. I didn't notice this > before because there was nothing at the end of adt-run's output that > would indicate that something went awry. > The

Re: autopkgtest'ing against multiple Python versions

2012-04-23 Thread Jakub Wilk
* Yaroslav Halchenko , 2012-04-23, 09:17: The “failures” was caused by the following misfeature of the specification: “if a test […] prints to stderr, it is considered to have failed.” But nosetests does print stuff to stderr even if everything is all right (see bug #460242). yikes -- doesn't i

Re: autopkgtest'ing against multiple Python versions

2012-04-30 Thread Brian Sutherland
On Sat, Apr 21, 2012 at 10:33:24PM +0200, Jakub Wilk wrote: > 3) Provide one test that is run against all installed versions > (pyversions -i): > > Tests: test-installed > Depends: python-pet-module > > This is a variant of 2 which is more friendly to users who can't or > don't want t

Re: autopkgtest'ing against multiple Python versions

2012-04-30 Thread Jakub Wilk
* Brian Sutherland , 2012-04-30, 19:47: How are you actually running the tests with adt-run. Did you actually setup a testbed, or is there now an easy way to run the tests? When you apply the patch from bug #648148, you can use your host system as testbed. You run this in an unpacked (and buil

Re: autopkgtest'ing against multiple Python versions

2012-06-14 Thread Ian Jackson
Jakub Wilk writes ("Re: autopkgtest'ing against multiple Python versions"): > * Yaroslav Halchenko , 2012-04-23, 09:17: > >>The “failures” was caused by the following misfeature of the > >>specification: “if a test […] prints to stderr, it is considered to