[Pyrex] Help for public Python extension types.

[Daehyok Shin]

Greg.
I found that I can solve the problem when I append xxx.yyy.zzz to the
file names of test.pxd and test.pyx.  However, the shared lib test.so
is created under ./xxx/yyy/zzz.
Because test.pyx and test.pxd are already in xxx/yyy/zzz, I don't want
to create another nested directory structure.  So, I want to have the
following package structure. Is there any way I can do it with Pyrex?

from xxx.yyy.zzz import test

xxx/
  yyy/
     zzz/
       test.pyx
       test.pxd
       test.so

Daehyok

On Sat, Jun 28, 2008 at 12:57 AM, Daehyok Shin <sdhyok at gmail.com> wrote:
> Greg.
> What I meant is that I have to be explicit in specifying package
> hierarchy when defining an extension type (or, as you suggested, its
> file name)? Since my source files are already inside a package
> directory structure, it is cumbersome to me. Cython seems not require
> it.
>
> Daehyok
>
> On Fri, Jun 27, 2008 at 9:23 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
>> Daehyok Shin wrote:
>>
>>> I am wondering why Pyrex forces users to use the complex name scheme
>>> for extension types.
>>
>> What complex naming scheme are you talking about?
>>
>> --
>> Greg
>>
>
>
>
> --
> Daehyok Shin, PhD
> Geography Department
> University of North Carolina-Chapel Hill
> USA
>



-- 
Daehyok Shin, PhD
Geography Department
University of North Carolina-Chapel Hill
USA