On Sat, Mar 31, 2012 at 3:22 PM, Immanuel B wrote:
> Thanks both of you,
>> Do `make inplace` for the incremental build only of the C files that
>> have changed since the last build and then use `nosetests
>> sklearn/mypackage/module` to launch the tests only on your module.
> this did the trick.
Thanks both of you,
> Do `make inplace` for the incremental build only of the C files that
> have changed since the last build and then use `nosetests
> sklearn/mypackage/module` to launch the tests only on your module.
this did the trick.
@David
I have dependencies linking them manually is somewha
Le 31 mars 2012 14:27, Immanuel B a écrit :
> Hello,
>
> I'm just starting to work on some cython files in scikit. It would
> great if someone could suggest
> me an easy way to compile them.
> Currently I'm running `cython` on the file and then make on
> scikit-learn. This seems to work but the se
Hi
On Sat, Mar 31, 2012 at 2:27 PM, Immanuel B wrote:
> I'm just starting to work on some cython files in scikit. It would
> great if someone could suggest
> me an easy way to compile them.
> Currently I'm running `cython` on the file and then make on
> scikit-learn. This seems to work but the se
Hello,
I'm just starting to work on some cython files in scikit. It would
great if someone could suggest
me an easy way to compile them.
Currently I'm running `cython` on the file and then make on
scikit-learn. This seems to work but the second
step is quite slow. I also tried to write a short set
