Lisandro Dalcin wrote: > On Wed, Feb 11, 2009 at 11:17 PM, Jason Evans <[email protected]> wrote: >> Ah, okay. I had to give up on the portability of Cython-generated code >> in order to add the ability to conditionally support mpi4py, so I >> haven't really been thinking in terms of portable Cython output lately. >> Thanks for the explanation. > > I do not understand you here. Why is mpi4py a source of problems? > mpi4py should work the same on all platforms. Well, we have MPI_Aint > and MPI_Offset, I'm currently using typedefs, but this is an approach > I have to review and fix ASAP.
The issue is that I need to be able to compile my software with the mpi4py code disabled (because it isn't a reasonable expectation that my users will always have MPI installed). There is no way I've found to make a cimport of a non-existent module safe, except to wrap it in an IF block. So, mpi4py is only indirectly the source of my problems, because it's the only third party Cython module I'm using at the moment. mpi4py looks like a great piece of software, and it has worked well for the limited testing I've done with it. Jason _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
