News for hackers. Stuff that matters.
Re:The optional “else” in Python loops by pyre on Thursday July 17, 2014 @11:41PM (#8051557)
I think the real issue is that the word 'else' is ambiguous in the context. Everyone comes in with a different idea of what the 'else' is a fallback clause to. Guido obviously picked one particular case, but there are other valid meanings.

For example, I think that it's more common to want to do something like:

  # mnemonic:
  #   for thing in list_of_things DO_SOMETHING else DO_SOMETHING_ELSE

  if list_of_things:
    for thing in list_of_things:
      print thing
  else:
    print "No things!"
Than:

  for thing in list_of_things:
    if thing.is_awesome:
      break
  else:
    print "No awesome things!"
And what about conditional code that you want to execute when a loop does break early?

  error_found = False

  for thing in list_of_things:
    if thing.error_condition:
      error_found = True
      break

  if error_found:
    pass
Re:The optional “else” in Python loops by collyw on Friday July 18, 2014 @03:52AM (#8052083)
That makes sense on one level, but when you consider Pythons indenting rules, it just messes everything up.
Re:The optional “else” in Python loops by pyre on Friday July 18, 2014 @01:32PM (#8054368)
I'm not sure how the indentation rules come into play here. I'm not saying that this:

  if blah:
    for .. in ..:
      ..
  else:
    ..
is visually confused with:

  for .. in ..:
    ..
  else:
    ..
What I'm saying is that for-else and while-else add syntax to the language that only solves a single specific instance of a class of similar issues, making it confusing.

Let's consider the issues that are in the same class:

- execute code block when loop condition isn't met the first time (i.e. loop never executes).

- execute code block when loop exits prematurely (e.g. break).

- execute code block when loop doesn't exit prematurely (e.g. no break) // execute code block when loop condition evals to false (first eval or any subsequent eval)

Only one of these issues is solved by the for-else/while-else syntax currently in Python, and using a generic keyword (else) just heightens the confusion (especially since this syntax differs from many other languages).

All of these cases may require the use of sentinels / additional checks to implement. Why is one specific instance any more relevant than the others to the point that it gets special treatment (i.e. special syntax in the core language)?