On Mon, Jan 27, 2014 at 6:44 PM, me <no...@all.net> wrote: > On Sun, 26 Jan 2014 23:17:29 -0800, Ethan Furman wrote: > >> On 01/26/2014 10:46 PM, me wrote: >>> >>> [...] I'm satisfied that the except: syntax yields undefined behavior, >>> and in my mind it shouldn't be >>> syntactically allowed then. >> >> Two points: >> >> 1) Python is not C++ >> >> 2) You asked for help; you received it. Coming back >> with an attitude of "Python must be broken, I'll work around it" >> is going to quickly lose you the support of those willing to help >> again. > > > Whatever...lighten up dude!
When you use a language, you should be working with it, not fighting against it. It doesn't do to complain that REXX ought to have IEEE floating-point semantics, or that 8086 assembly language really would benefit from a native hashtable type. Python works a certain way, and part of that is its use of exceptions - which are integral to the language, rather than being (as in C++) somewhat tacked-on. Assuming that anything that isn't the way you expect it is inherently broken, and saying so on a mailing list, is a good way to alienate those who are offering you help for no reimbursement... and "lighten up dude" doesn't help. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
