Ethan Furman writes:
> If you don't get an answer here, you can try the Cython Users group:
Thanks, reposted the same question there.
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
Greg Ewing writes:
> You could try creating a set of top-level .pyx stubs, each of
> which just 'include' the real code.
Thank you, will try this approach!
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi
On 20/12/19 2:16 am, Lele Gaifax wrote:
My first approach has been duplicating the Extension() entry in the
setup.py(*), changing the first argument (that is, the name of the module).
Although that did produce the alternative binary module, it could not be
loaded because it contains the wrong
On 12/19/2019 05:16 AM, Lele Gaifax wrote:
in my package, I would like to compile and distribute two different extension
modules starting from the same .pyx file, just with different compilation
flags and libraries.
If you don't get an answer here, you can try the Cython Users group:
Hi all,
in my package, I would like to compile and distribute two different extension
modules starting from the same .pyx file, just with different compilation
flags and libraries.
My first approach has been duplicating the Extension() entry in the
setup.py(*), changing the first argument (that
