Felix Salfelder, 25.08.2013 20:54:
> On Sun, Aug 25, 2013 at 08:08:50PM +0200, Stefan Behnel wrote:
>> OTOH, there's a "force" option (both in distutils and cythonize()) that you
>> can use when you know something relevant changed and want to rebuild
>> everything.
>
> In huge projects one usually
On Sun, Aug 25, 2013 at 08:08:50PM +0200, Stefan Behnel wrote:
> > This might be a bug, depending on whether cythonize is meant to refresh
> > output files consistently.
>
> May not really be a bug, but the current dependency tracking has its
> limits, yes.
>
> Another issue is that it doesn't re
Felix Salfelder, 25.08.2013 16:52:
> Lets say, i have foo.pyx. and use cythonize() to generate foo.c.
> Calling cythonize() a second time will correctly do nothing, because
> foo.c has been modified after foo.pyx.
>
> If I now add foo.pxd, cythonize will correctly update foo.c. In general
> foo.c
Hi there.
Lets say, i have foo.pyx. and use cythonize() to generate foo.c.
Calling cythonize() a second time will correctly do nothing, because
foo.c has been modified after foo.pyx.
If I now add foo.pxd, cythonize will correctly update foo.c. In general
foo.c now looks different. But: Deleting f
