On Tue, 25 Nov 2003 13:15:48 -0800 "Sean R. Lynch" <[EMAIL PROTECTED]> wrote:
> 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. Good idea ! > Blam and Jiba, are you OK with this? I know you know the Python C API > very well, Blam knows it well, but not myself :-) > but I think Pyrex code would be much more maintainable even > for the two of you. Sure ! Though i'm not convinced that the all Python part must be rewritten in Pyrex. E.g. the pickling stuff is really complex and file loading is IMHO fast enough. Cloning / copying stuff enter in the same category. Other modules like the facecutter are really specific and only used at design time, so i believe they don't worth conversion, at least in a first time. We must also take care of keeping REAL python class, so as we can extend them in pure python, and using mutiple inheritance and mixins. The problem will be to find your way in the C code, because it is quite a mess... What do you think of that Blam ? If you start any work, use the CVS version (which has lots of changes from the last release). Jiba -- Pour vous desabonner envoyez un mail a [EMAIL PROTECTED]
