Re: [Cython] trouble splitting extension type into definition and implementation files

2009-05-21 Thread Greg Ewing
Robert Bradshaw wrote: > I don't know how it works on Windows, but on linux/OS X Python does a > lookup on modulename.so as part of the import mechanism... Perhaps > some hackery could be done, but it wouldn't work out of the box. Possibly it could be made to work by having the init code of t

Re: [Cython] trouble splitting extension type into definition and implementation files

2009-05-21 Thread Greg Ewing
Chris Colbert wrote: > What I want to be able to do, is have all of my multiple .pyx and .pxd > files compiled and built into a single .pyd If you're keeping them as separate modules, you end up with a .pyd for each module, and the setup.py has a separate Extension instance for each module. Yo

Re: [Cython] trouble splitting extension type into definition and implementation files

2009-05-21 Thread Robert
Chris Colbert wrote: > so, what would the setup script look like for something like this? > > if i do: > > sources = ['file1.pyx', 'file2.pyx', ... ] > > setup( > cmdclass = {'build_ext': build_ext}, > ext_modules = [Extension("mymodule", sourcefiles, > in

Re: [Cython] trouble splitting extension type into definition and implementation files

2009-05-21 Thread Robert Bradshaw
On May 21, 2009, at 9:52 AM, Chris Colbert wrote: > so, what would the setup script look like for something like this? > > if i do: > > sources = ['file1.pyx', 'file2.pyx', ... ] > > setup( > cmdclass = {'build_ext': build_ext}, > ext_modules = [Extension("mymodule", sourcefiles, >

Re: [Cython] trouble splitting extension type into definition and implementation files

2009-05-21 Thread Chris Colbert
so, what would the setup script look like for something like this? if i do: sources = ['file1.pyx', 'file2.pyx', ... ] setup( cmdclass = {'build_ext': build_ext}, ext_modules = [Extension("mymodule", sourcefiles, include_dirs=include_dirs,

Re: [Cython] trouble splitting extension type into definition and implementation files

2009-05-20 Thread Greg Ewing
Chris Colbert wrote: > Is there a way to properly compile everything into a single .pyd, You can use include statements to split a .pyx into multiple files, but I wouldn't recommend that, because it makes it hard for the reader to tell where things are defined. Also, separate modules means there

Re: [Cython] trouble splitting extension type into definition and implementation files

2009-05-20 Thread Chris Colbert
Ok, so compiling each .pyx file into an individual .pyd worked. Is there a way to properly compile everything into a single .pyd, or should I create a dummy module at the end that imports each individual module when called from python? Chris ___ Cython-

[Cython] trouble splitting extension type into definition and implementation files

2009-05-20 Thread Chris Colbert
Hi, I have this definition file: cy_cvtypes.pxd # cimport c_cxcore cimport c_highgui cdef class IplImage: cdef c_cxcore.IplImage* thisptr cdef int needs_free ### and the corresponding implementation: cy_cvtypes.pxy ## cimport c_cxcore cimpo