Hi, Lisandro Dalcin wrote: > The last four hours (3:00 AM right now here at Argentina) I've been > working in a patch for enabling Cython generate code working with > Python 2.6 and Python 3.0. > > Until now, the generated code (at least for the full mpi4py project) > compiles and link fine with no errors. > > However, I have a big problems I do not know how to 'fix' in Cython. > It is related to unbound methods disapearing in Py3K. Then, normal > python classes does not work, but the cdef ones are fine.
These are the kind of things that we planned to address at the dev1 workshop. The C-API of Python is expected to stabilize next month, I don't know how stable these parts currently are. > Is there any interest on this to go mainstream? Sure, totally! > I was very > conservative about the PyString/PyUnicode issue. The right one is used > in a place-by-place base. Of course, because of this, I have to pass > 'bytes' to MPI, and I get 'bytes' from the C calls. Yes, I think this is the right way to deal with it. Python2 was very lax in terms of semantics here, so the two have to be separated on a case-by-case basis. > Finally, I'm completelly sure that I've not fixed all the relevant > parts, but this is IMHO a good starting point. Is it one big patch or did you/can you split it up? As this is potentially a big change, trac is the wrong place to discuss it. We should put up an official Py3 branch that people can actively work on without impacting the main trunk, so that we can merge working stuff gradually. Can you send a bundle against cython-devel to me and Robert for now? He can set it up. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
