On 12/07/2014 05:00 PM, Juan Nunez-Iglesias wrote:

A bunch of Travis errors are being caused (apparently) by travis-wheels.scikit-image.org not responding. I haven't been following the discussion closely, but my question is, do we need to get rid of it for the Travis build so that we can have a stable build system at the sprint? Or do we perhaps want to add a condition to use regular pip builds if travis-wheels is unavailable?

--
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.

We know have http://wheels.scipy.org/ which has OS-X and Linux wheels for many SciPy stack modules. http://travis-wheels.scikit-image.org/ still responds for me and seems to have more files than the scipy.org domain. Github issue #1057 is where we are discussing the wheels, Windows CI, and related topic, https://github.com/scikit-image/scikit-image/pull/1057. If there are files you need at either site I can add them easily.

Cheers,

- Jonathan Helmus