Am 27.04.2012 23:57, schrieb Aaron Meurer:
There is a label in the issue tracker, "Testing", that should be on
all testing related issues (just search for "label:Testing").
Okay, finished reading.
From the issues, it seems to me that it would be easier to solve any
problems SymPy may have with upstream pytest and drop our own pytest
fork, than to keep up with upstream pytest just to stay compatible with
standard CI frameworks or anything else we might want to integrate
testing with.
( http://code.google.com/p/sympy/issues/detail?id=2542 is the issue for
doing that, is that correct?)
The other impression that I got is that everybody is fixing what's
hurting them right now.
That's okay, but since we have no list of desiderata and no list of
what's more important and what's less important, people risk building
code that doesn't interoperate well.
I have set up a page in the wiki to collect these lists. Sorry for
charging ahead here, but when I started writing down stuff in this
message, I thought it could just as well go into the wiki page.
It is on https://github.com/sympy/sympy/wiki/Test-automation .
Please add anything that I have missed!
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from this group, send email to
sympy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sympy?hl=en.
