![](https://secure.gravatar.com/avatar/2c1bbda1fbfa050465bc2a4448866c09.jpg?s=120&d=mm&r=g)
Awesome, thanks a lot. Let's do it soon. There are more things - Kirill (another developer of SymPy) implemented a new feature:
http://code.google.com/p/sympy/issues/detail?id=389
the relevant file is here:
http://sympy.googlecode.com/svn/trunk/sympy/utilities/pytest.py
and we would like to get it integrated to py.test. It works really well for us in the serial mode, but it doesn't yet work in the "py.test -d" mode. And now I found it doesn't work in the boxed mode, so it still needs some work.
Another problem: "py.test -w" doesn't work in Debian, I reported a bug long time ago:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434226
But got no response. I am CCing to the Debian maintainer - if you don't have time to maintain the package, I can take over it, I have several python related packages in Debian already and I need the py.test to work correctly if possible.
Another problem with "py.test -d" is that it fails for sympy, but "py.test" only works. This is related to my last email, so by implementing bisect at least in serial mode should help me to trace all those nasty bugs in sympy down. One nice feature would be for py.test to remember the order of tests in "py.test -d" - and if it fails, but succeeds in the serial mode, it should automatically bisect and tell me - hey, this test works fine, but if executed just after that test, it fails.
Ondrej Ok, I'll take a look. Would be cool to have nice and working debian
Ondrej Certik wrote: package, but indeed we're not good in packaging. Also, we would like to do 1.0 release at some point. The main blocker is some refactorings to-be-done (some internal unification) and eventually unittest support and/or cross-platform testing (like -d, but run every test per every platform). Cheers, fijal :.