Re: Help for public Python extension types.

Stefan. It did not work in that way with the most recent version of Pyrex.
This is what I understand from the previous replies.
1. You have to rename test.pyx and test.pxd to xxx.yyy.zzz.test.pyx
and xxx.yyy.zzz.test.pxd.
2. If you leave the files under zzz directory, you have the following
directory structure.
xxx/
  yyy/
     zzz/
         xxx.yyy.zzz.test.pyx
         xxx.yyy.zzz.test.pxd
         xxx/
            yyy/
               zzz/
                  test.so

So, we have another deep path. I am trying to find a way not to create
the redundant path.
Thanks for your interest.

Daehyok

On Sat, Jun 28, 2008 at 1:32 AM, Stefan Behnel <[email protected]> wrote:
>
> Daehyok Shin wrote:
>
> The xxx/yyy/zzz/test.pyx in
>
>> xxx/
>    __init__.py
>>   yyy/
>       __init__.py
>>      zzz/
>         __init__.py
>>        test.pyx
>>        test.pxd
>
> should compile just fine and create a
>
> xxx/
>  yyy/
>     zzz/
>>        test.so
>
> that you can import as
>
>> from xxx.yyy.zzz import test
>
> Are you using distutils?
>
> Stefan
>
>



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