Mark> * Catching "return" and "return expr" at compile time Mark> Seemed to be blessed - yay! Dont believe I have seen a check-in Mark> yet. I did post a patch to compile.c here and to the announce list. I think the temporal distance between the furor in the main list and when it appeared "in print" may have been a problem. Also, as the author of that code I surmised that compile.c was the wrong place for it. I would have preferred to see it in some Python code somewhere, but there's no obvious place to put it. Finally, there is as yet no convention about how to handle warnings. (Maybe some sort of PyLint needs to be "blessed" and made part of the distribution.) Perhaps python-dev would be good to generate SIGs, sort of like a hurricane spinning off tornadoes. Skip Montanaro | http://www.mojam.com/ skip@mojam.com | http://www.musi-cal.com/ 847-971-7098 | Python: Programming the way Guido indented...