[Cython] Problems with creating a package of extension modules

[Robert Bradshaw]

On May 1, 2009, at 12:30 PM, Simon King wrote:

> Dear Robert,
>
> Zitat von Robert Bradshaw <robertwb at math.washington.edu>:
>> Hmm... could you point me to that bit of documentation? I think it's
>> wrong (or at least not implemented as explained), we do Extension
>> ("package.module",...) all the time in sage and that seems to mix
>> well with pickling.
>
> Admittedly it is not Cython-documentation, but Python:
> At http://docs.python.org/distutils/setupscript.html, they say:
>
> ---------------------
> If you have a number of extensions all in the same package (or all  
> under the
> same base package), use the ext_package keyword argument to setup 
> (). For
> example,
>
> setup(...,
>       ext_package='pkg',
>       ext_modules=[Extension('foo', ['foo.c']),
>                    Extension('subpkg.bar', ['bar.c'])],
>      )
>
> will compile foo.c to the extension pkg.foo, and bar.c to  
> pkg.subpkg.bar.

To wrap this thread up, it turns out that the ext_package option is  
incompatible with using .pxd files. Without the ext_package  it works  
as expected (One complication--when trying stuff like this out, one  
has to make sure to delete the .c file as well as the build directory.)

- Robert