I'm willing to handle the work for ODE integration, but before I do that
I'd like to rewrite the Python-specific parts of Soya in Pyrex [1],
including the pure Python parts (except the examples and tutorials,
obviouslY). This would allow people to work on Soya without learning the
Python C API, and it would make the Python/C interface files much more
readable and much shorter. It would also probably make Soya a bit
faster, since all of Soya would then be compiled code. At the same time,
I'd like to add a bunch more error checking to try to reduce the number
of times Soya segfaults when given bogus data from Python.
Blam and Jiba, are you OK with this? I know you know the Python C API
very well, but I think Pyrex code would be much more maintainable even
for the two of you.
Footnotes
1. <http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/>
begin:vcard
fn:Sean Lynch
n:Lynch;Sean
email;internet:[EMAIL PROTECTED]
tel;work:+1 408 921 8183
tel;home:+1 408 377 0668
tel;cell:+1 408 921 8183
x-mozilla-html:FALSE
version:2.1
end:vcard
pgp00000.pgp
Description: PGP signature
