Repository for GSoC project

[Ralf Gommers]

On Tue, May 26, 2015 at 6:00 PM, Jaime Fernández del Río <
jaime.frio at gmail.com> wrote:

>
> You received this message because you are subscribed to the Google Groups
> "scikit-image" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to scikit-image+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> Thanks everyone for the feedback. After some more thinking, I have asked
> Aman to start sending PRs directly against the current master of scipy.
>
> To differentiate new from old implementations, we'll probably just prepend
> all file names with "ndi_" instead of the current "ni_". We will eventually
> start removing old functionality that has been replaced, but for quite
> sometime they will both coexist. This means that at some point in time,
> e.g. calling `ndimage.filters.uniform_filter1d` may use the new Cython code
> paths, while `ndimage.filters.minimum_filter1d` may still be using the old
> C code paths.
>
> We will not merge anything, answering Juan's question, until we have tests
> that validate that functionality. That does not mean that the functionality
> will be available to end users just yet, e.g. we may merge an iterator
> before any top level function that uses it. But if it does not have tests,
> it does not get merged.
>
> If anyone has a very strong opinion against this approach, please speak up
> now!
>

I like this. If you can keep old and new implementations side by side, it
could even be a good idea to have an easy mechanism (clearly marked as
temporary and only for testing) for users to switch between the two so they
can test their own code with the new routines before those become the
default.

Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-image/attachments/20150528/5b08e250/attachment.html>