![](https://secure.gravatar.com/avatar/66cfe7cb676bbd44769ebc394f2ecac9.jpg?s=120&d=mm&r=g)
I attended the scikits.image sprint and we agreed to let Cython be dependency. At the sprint, I wrote integral image and morphology code available, which is available here http://github.com/deads/scikits.image/tree/master/scikits/image/filter/ http://github.com/deads/scikits.image/tree/master/scikits/image/morphology/ Stefan has been trying to get me to merge it back in but I haven't had the time to figure out how to do this with GIT. Damian On Sat, Oct 3, 2009 at 11:38 PM, Chris Colbert <sccolbert@gmail.com> wrote:
would you mind pointing it out to me?
I scanned through the entire source tree here: http://github.com/stefanv/scikits.image
but didn't see anything...
Sorry if I'm just not seeing it....
-Chris
On Sun, Oct 4, 2009 at 12:33 AM, Damian Eads <eads@soe.ucsc.edu> wrote:
On Sat, Oct 3, 2009 at 11:22 PM, Chris Colbert <sccolbert@gmail.com> wrote:
i.e. Do we want to standardize how we will implement the functionality in the Image Kit or are we free to use whatever tools we are familiar with?
Personally, I do most performance related stuff with Cython, so are we ok to require Cython as a build dependency? Or would we rather limit things to python and the C api only?
Code already exists in scikits.image which depends on Cython.
Damian
-- ----------------------------------------------------- Damian Eads Ph.D. Candidate University of California Computer Science 1156 High Street Machine Learning Lab, E2-489 Santa Cruz, CA 95064 http://www.soe.ucsc.edu/~eads