+1 for optional dependency, but only if optional. My motivation: - possibly better underlying graph library than using our own quick implementation (though, I am not too familiar with networkx) - much faster progress in GSoC project Johannes Schönberger On Jun 11, 2014, at 11:22 AM, Ronnie Ghose <ronnie.ghose@gmail.com> wrote:
+1 as an optional module for additional functionality - I'm not a fan of monolithic libraries
On Jun 11, 2014 11:18 AM, "Juan Nunez-Iglesias" <jni.soma@gmail.com> wrote: Hi all,
We are trying to make a pretty big decision regarding the API for graph segmentation methods as part of Vighnesh's GSoC project. The main question is whether to implement our own graph class and build on that, or to use networkX. This would add a (potentially optional) dependency to skimage, but would use established classes an APIs.
Here's where the relevant discussion on the skimage-gsoc mailing list starts:
https://groups.google.com/d/msg/skimage-gsoc/sAhf0ecpHXM/io2LxCU8VC8J
As such a decision has a major impact on the skimage API going forward, please take some time to respond to this!
Thanks,
Juan.
-- 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@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
-- 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@googlegroups.com. For more options, visit https://groups.google.com/d/optout.