Greg Ewing greg at cosc.canterbury.ac.nz
Wed Oct 22 19:35:52 EDT 2003

• Previous message: [Python-Dev] listcomps vs. for loops
• Next message: [Python-Dev] listcomps vs. for loops
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Guido:

> The variable of a for *statement* must be accessible after the loop
> because you might want to break out of the loop with a specific
> value.  This is a common pattern that I have no intent of breaking.

It wouldn't be a great hardship if the loop variable
weren't accessible after the break, because you can
always write

  for x in stuff:
    if meets_condition(x):
      result = x
      break
  do_something_with(result)

which is arguably a clearer way to write it, anyway.

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg at cosc.canterbury.ac.nz	   +--------------------------------------+

---

• Previous message: [Python-Dev] listcomps vs. for loops
• Next message: [Python-Dev] listcomps vs. for loops
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list