On Sun, Mar 05, 2017 at 01:17:31PM +1000, Nick Coghlan wrote:
> I forget where it came up, but I seem to recall Guido saying that if he
> were designing Python today, he wouldn't include the "else:" clause on
> loops, since it inevitably confuses folks the first time they see it.
Heh, if we
On 03.03.2017 09:47, Wolfgang Maier wrote:
However, the fact that else exists generates a regrettable asymmetry
in that there is direct language support for detecting one outcome,
but not the other.
Stressing the analogy to try/except/else one more time, it's as if
"else" wasn't available
On 03/03/2017 04:36 AM, Nick Coghlan wrote:
On 2 March 2017 at 21:06, Wolfgang Maier
> wrote:
- overall I looked at 114 code blocks that contain one or more breaks
Thanks for doing that research :)
On 3/1/17, Wolfgang Maier wrote:
> - as explained by Nick, the existence of "except break" would strengthen
> the analogy with try/except/else and help people understand what the
> existing else clause after a loop is good for.
I was thinking bout this
On 1 March 2017 at 06:37, Wolfgang Maier
wrote:
> Now here's the proposal: allow an except (or except break) clause to follow
> for/while loops that will be executed if the loop was terminated by a break
> statement.
After rethinking over some code I've
On 1 March 2017 at 19:37, Wolfgang Maier <
wolfgang.ma...@biologie.uni-freiburg.de> wrote:
> I know what the regulars among you will be thinking (time machine, high
> bar for language syntax changes, etc.) so let me start by assuring you that
> I'm well aware of all of this, that I did research
On 03/01/2017 01:37 AM, Wolfgang Maier wrote:
Now here's the proposal: allow an except (or except break) clause to follow
for/while loops that will be executed if the
loop was terminated by a break statement.
I find the proposal interesting. More importantly, the proposal is well
written
> On 2017 Mar 1 , at 4:37 a, Wolfgang Maier
> wrote:
>
> I know what the regulars among you will be thinking (time machine, high bar
> for language syntax changes, etc.) so let me start by assuring you that I'm
> well aware of all of this, that I did
I know what the regulars among you will be thinking (time machine, high
bar for language syntax changes, etc.) so let me start by assuring you
that I'm well aware of all of this, that I did research the topic before
posting and that this is not the same as a previous suggestion using
almost