Re: [Python-Dev] the current behavior of try: ... finally:
It did surprise me also. Because I've come to Python from Delphi. There are no return statement in Delphi. I also write some c++, the language has no finally-statement. This problem probably python exclusive. I think it's not too difficult to get used to it. This behavior is fine for me. ___ 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
Re: [Python-Dev] the current behavior of try: ... finally:
Michele Simionato wrote: def divide1(n1, n2): try: result = n1/n2 finally: print cleanup result = Infinity\n return result # the exception is swallowed away What would you prefer to have happen in this case? Or do you think return (and break and continue) should be disallowed in a finally? -- Greg Ewing, Computer Science Dept, +--+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | [EMAIL PROTECTED] +--+ ___ 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
Re: [Python-Dev] the current behavior of try: ... finally:
On 5/13/05, Greg Ewing [EMAIL PROTECTED] wrote: Michele Simionato wrote: def divide1(n1, n2): try: result = n1/n2 finally: print cleanup result = Infinity\n return result # the exception is swallowed away What would you prefer to have happen in this case? Or do you think return (and break and continue) should be disallowed in a finally? Honestly, I don't know. This is why I ask here ;) Michele Simionato ___ 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
