btw, all your changes look good.<br><br><div class="gmail_quote">On Fri, Nov 5, 2010 at 9:29 AM, Chris Colbert <span dir="ltr">&lt;<a href="mailto:sccolbert@gmail.com">sccolbert@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Did we decided on a standard for which dtypes we will support? <div><br></div><div>Some of the color conversions can be sped up in Cython with a lut (ala scivi), but we would need to write one func for each dtype.</div><div>

<br></div><div>I am working on a webinar for image processing and am getting back into using th scikit, so there are some things I&#39;m seeing during use that I would like to improve, but would require knowledge of what dtypes to support.</div>

<div><br></div><div>Chris <br><br><div class="gmail_quote">2010/11/5 Stéfan van der Walt <span dir="ltr">&lt;<a href="mailto:stefan@sun.ac.za" target="_blank">stefan@sun.ac.za</a>&gt;</span><div><div></div><div class="h5">
<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
At the SciPy sprint (ages ago), Chris suggested that we clean up the<br>
image loading API.  The following changes simplify `imread` by<br>
removing the `dtype` argument.  This allows for simpler plugins.<br>
Because `as_grey` is such a commonly used parameter, it is left in<br>
place, but now works differently: after the image is loaded, the (new)<br>
rgb2grey is simply performed on it.<br>
<br>
Please have a look at<br>
<br>
<a href="https://github.com/stefanv/scikits.image/compare/master...io_cleanup" target="_blank">https://github.com/stefanv/scikits.image/compare/master...io_cleanup</a><br>
<br>
Regards<br>
<font color="#888888">Stéfan<br>
</font></blockquote></div></div></div><br></div>
</blockquote></div><br>