> > 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. > > Pyrex classes are Python classes, so this is no problem.
Yes but there are several kinds of Python class... C coded class are Python class but are not as powerfull as Python one. > > 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 ? > > Most of the C code will convert straight across with just a syntax > change. Decoding the Python C API calls will probably be the hardest. It > would also be nice if Pyrex would decode .h files, but that doesn't even > work well with SWIG, so I should count my blessings :) The problem is that soya doesn't use Python object in its core, but "p3 object", a hackish object system developped by blam and specific to soya... removing this useless layer of "p3 object" may be interesting, at least for Python objects. > > If you start any work, use the CVS version (which has lots of changes > > from the last release). > > I have been using the CVS version for everything I've been doing. > > I will probably have Land converted over within a couple of days, since > that's the C code I've spent the most time looking at. The time is due > to work and the holiday, not because of difficulty :) > > The land.py file will end up looking like: > > import _soya > > Land = _soya.Land > > :) Good ! We are about releasing soya (there's still some bugs that i want to fix ; yes i am aware that we are "about releasing" since more than one month :-( ), so this will probably fit in the next release. Jiba -- Pour vous desabonner envoyez un mail a [EMAIL PROTECTED]
