Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #7778 > unrolled thread
| Started by | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| First post | 2011-06-16 17:57 -0600 |
| Last post | 2011-06-16 17:57 -0600 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: break in a module Ian Kelly <ian.g.kelly@gmail.com> - 2011-06-16 17:57 -0600
| From | Ian Kelly <ian.g.kelly@gmail.com> |
|---|---|
| Date | 2011-06-16 17:57 -0600 |
| Subject | Re: break in a module |
| Message-ID | <mailman.47.1308268695.1164.python-list@python.org> |
On Tue, Jun 14, 2011 at 4:57 PM, MRAB <python@mrabarnett.plus.com> wrote: > To me, the obvious choice would be "return", not "break". No, "return" returns a value. Modules do not return values. Therefore "return" would be inappropriate. If this feature were deemed desirable, "break" would make more sense to me.
Back to top | Article view | comp.lang.python
csiph-web