>>>>>> * Preparation is being made for making 'not None' the >>>>>> default for extension type parameters to Python functions.
>>> I guess I should repeat my big -1 for this then. >>> >>> I think Java-like behaviour is much more appropriate (i.e. raise proper >>> exceptions in the code using the variable, but allow None as a value). I'm a bit confused here -- how could you have the code checking for None everywhere without a performance hit? I understand the utility of being able to pass None, but it is really dangerous unless it is handled properly, which means the user code needs to check for it up front. >> Would you accept a directive to ENABLE automatic "not None"? That seems reasonable to me -- by the way, is there a deprecation policy for Cython? > And "not None" is already in the syntax. "Explicit is > better than implicit" and all that. Sure, but leaving it out is not explicit, and it is the more dangerous option. An "allow None" would be the right way to be explicit. -just a couple thoughts from a user. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected] _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
