Or perhaps we could do thing like this: #ifndef PYX_MODULE_NAME #define PYX_MODULE_NAME "mypkg.mymod" #endif
and use the macro PYX_MODULE_NAME in the generated sources. And of course, if the user pass the -D flag to the compliler and next this breaks 'cimport', please do not blame us ;-). On Wed, Oct 29, 2008 at 9:11 AM, Stefan Behnel <[EMAIL PROTECTED]> wrote: > Stephane DROUARD wrote: >> There are maybe some other situations where Pyrex/Cython hardcodes the >> module name in the generated code, but I'm quite confident that they can >> be replaced by the module's name retrieved at runtime. > > I'm not sure this is the case for cimports of external extension types > (which are imported at runtime). This will have to be verified before such > a change can be accepted. > > Stefan > > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > -- Lisandro Dalcín --------------- Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594 _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
