On Mon, Apr 2, 2018, at 6:59 AM, Stefan van der Walt wrote: > On Sun, 01 Apr 2018 13:47:41 -0400, Juan Nunez-Iglesias wrote: > > Ralf’s comment in particular gives me pause again about my magical > > proposal. Changing that behaviour could indeed be simply trading one > > class of common error for another, even more annoying class. > > It's worse than that: it prevents one specific use-case (the one Ralf > mentioned, e.g., where you have very low signal, but correctly so).
No: we are arguing about default behaviour. I would always envision having the option to turn this off. > I am strongly in favor of more expansive warning and error messages. Great! > > - put a big warning on the project homepage: “black images? out of > > range errors? See this page!” The page would be the data types page, > > to which we must add a “troubleshooting common data type errors” > > section. > > An FAQ section in the docs, linked to from the front page? Yes! Stéfan, btw, one last Q: what do you think about my suggestions for the (u)int32 and (u)int64 image types? I feel like assuming a range up to 2**32 when converting is *never* useful. _______________________________________________ scikit-image mailing list scikit-image@python.org https://mail.python.org/mailman/listinfo/scikit-image
