Stefan Behnel wrote:
The main reason we didn't change this behaviour back then was that it would clearly break user code and we thought we could do without that. That's different from considering it "right" and "good".
I changed the None-checking behaviour in Pyrex because I *wanted* to break user code. Or rather, I didn't think it would be a bad thing to make people revisit their code and think properly about whether they really wanted to allow None in each case. -- Greg _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
