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 numerodix
Recipients James.Lu, numerodix
Date 2013-10-20.18:36:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382294179.2.0.772931257148.issue19318@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2013-10-20 18:36:19numerodixsetrecipients: + numerodix, James.Lu
2013-10-20 18:36:19numerodixsetmessageid: <1382294179.2.0.772931257148.issue19318@psf.upfronthosting.co.za>
2013-10-20 18:36:19numerodixlinkissue19318 messages
2013-10-20 18:36:18numerodixcreate