"defcon8" wrote:
>I can't remember the proposal number, but many of you reading will have
> probably read the features that will be added to python 2.5. The actual
> part I wanted to talk about was the finally part of try. Isn't it
> totally defeating a compiler's job by executing the finally part
defcon8 wrote:
> I can't remember the proposal number,
http://docs.python.org/dev/whatsnew/pep-341.html
but many of you reading will have
> probably read the features that will be added to python 2.5. The actual
> part I wanted to talk about was the finally part of try.
It has been here from th
Hi,
defcon8 wrote:
> I can't remember the proposal number, but many of you reading will have
> probably read the features that will be added to python 2.5. The actual
> part I wanted to talk about was the finally part of try. Isn't it
> totally defeating a compiler's job by executing the finally
I can't remember the proposal number, but many of you reading will have
probably read the features that will be added to python 2.5. The actual
part I wanted to talk about was the finally part of try. Isn't it
totally defeating a compiler's job by executing the finally part even
if there is an erro
