Am 10.04.2014 06:03, schrieb Matthew Rocklin:
Yeah, that's pretty fantastic. I'm curious to know how much work was
involved. Is it possible to push your changes back to our codebase? We'd
be happy to enable this.
We'd need to run automated testing on Windows make it worth it;
otherwise, we're going to inadvertently add another IronPython problem
any day, which isn't going to make SymPy very useful.
Travis seems to be preparing for multiple OSes, newer entries in
https://github.com/travis-ci/travis-ci/issues/216 sound like it's Real
Soon Now(tm); it could till take a few months until it's really there
though.
The other approach would be Mono. Travis would like to support that as
well (see https://github.com/travis-ci/travis-ci/issues/649 ), but
that's been hitting roadblocks and seems to be inactive.
I'd be +1 on running tests on Windows and MacOS as soon as Travis
supports that.
It would triple the running time of tests, unfortunately. I'm not sure
how bad that really is. On the plus side, we could state better
guarantees for platforms.
For IronPython, I'm not -1 but I'd like to see some things verified.
I'm not sure how viable the project is actually. IronPython was created,
adopted by MS, then dropped again; any project will suffer from such a
history (it might actually have sorted out the fallout). Also, there
might be performance issues - IronPython is sometimes faster, sometimes
slower than CPython. OTOH I guess people will prefer a slow SymPy over
no SymPy so that's not a biggie (but we'll want to check the Travis
running times).
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sympy.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sympy/534636C1.4090905%40durchholz.org.
For more options, visit https://groups.google.com/d/optout.
