This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author James.Lu
Recipients James.Lu, numerodix
Date 2013-10-20.18:40:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Big example:
pygame, event proccessing loop running. the user clicks "Quit", you do
break 2.
while True:
    for event in
        if event.type==pygame.QUIT:
            break 2


On Sun, Oct 20, 2013 at 2:36 PM, Martin Matusiak <>wrote:

> Martin Matusiak added the comment:
> I see one potential problem with this, namely that refactoring code that
> contains "break n" statements would become more error prone whenever the
> depth of the code block gets modified. So if you had something like:
> for i in range(10):
>     for j in range(10):
>         for k in range(10):
>             if cond:
>                 break 2
> And then you decided to remove the middle loop (on j), the break 2 would
> send you to the top level, whereas you might have meant for it to break to
> the first level, inside the loop on i.
> This is a micro example, of course, but if you imagine the bodies of these
> loops being quite long then it could get complicated fast.
> ----------
> components: +Interpreter Core
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2013-10-20 18:40:59James.Lusetrecipients: + James.Lu, numerodix
2013-10-20 18:40:59James.Lulinkissue19318 messages
2013-10-20 18:40:59James.Lucreate