On Friday 04 March 2005 14:35, Raymond Hettinger wrote: > Hmm, more than one poster found the error message to be helpful in > detecting buggy code. The non-None return value was a pretty good > indicator that the code was doing something other than what the > programmer intended. > > OTOH, there is almost certainly some existing, working code that would > stop working. > > How about changing this to a warning in Py2.4?
+1 That would seem to be the prudent choice. -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
