Stefan Behnel wrote: > So the new default is not that "not None" applies, the new default is that > the type check for a Python argument is strict. So None is a valid value > for an 'object' typed argument, whereas it's not valid for some 'MyExtType' > argument.
Yes, that's probably the best way of looking at it. The 'or None' and 'not None' are about types, not values. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
