additional few cents which might come handy if you decide to go that way 1. I would recommend to override matplotlib backend to Agg before running tests
2. set HOME to build/ (or some other temp directory) to prevent common problems for those projects which use matplotlib in some of the tests if interested in how I do it, here would be an example: https://github.com/neurodebian/pandas/blob/debian/debian/rules#L54 On Mon, 30 Apr 2012, Yaroslav Halchenko wrote: > > will appear. One of challenges will be determining dependencies > > required during build process. > With such a massive automated "packaging" it would be great if from day > 0 you would think about adding build-time testing into the > pipeline. It should be quite easy to discover if module carries any > unittests (grep for unittest ;) ) and what should be the way to run them > (many modules provide .test(), or are testable with 'nosetest module'). > It would provide you assurance that generated packages are usable by the > users, thus reduce future frustration / bug reports about broken > packages. > Just my .1 cents. -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120430161358.gy9...@onerussian.com
