The following code:
for a in range(26):
for b in range(26):
for c in range(26):
for d in range(26):
for e in range(26):
for f in range(26):
for g in range(26):
for h in range(26):
for i in range(26):
for j in range(26):
for k in range(26):
for l in range(26):
for m in range(26):
for o in range(26):
for p in range(26):
for q in range(26):
for r in range(26):
for s in range(26):
for t in range(26):
for u in range(26):
for v in range(26):
for w in range(26):
pass
fails to compile with SystemError:too many statically nested blocks, which was described as a serious bug in bpo-27081.

There is a static limit for the number of statically nested blocks. Getting rid of this limit looks not easy.

But SystemError is not an exception that should be raised. SystemError is for errors that can't be occurred in normal case. It should only be caused by incorrect use of C API or hacking Python internals. I think SyntaxError is more appropriate in this case (as in case of passing more than 255 arguments to a function).

+1 for Serhiy's recommendation. It's OK for the compiler to say "Don't do that", but the correct error is SyntaxError, even when it's a limitation later in the code generation pipeline (rather than failing to comply with the language grammar)

This patch changes it to a SyntaxError instead of a SystemError.

Amended patch with the comment fixed to refer to just the issue numbers according to advice from bitdancer.

LGTM.

New changeset e6e7c8368c70 by Benjamin Peterson in branch '3.5':
make too many nested blocks be a SyntaxError instead of a SystemError (closes bpo-27514)
https://hg.python.org/cpython/rev/e6e7c8368c70

New changeset 345ec7455b75 by Benjamin Peterson in branch '2.7':
make too many nested blocks be a SyntaxError instead of a SystemError (closes bpo-27514)
https://hg.python.org/cpython/rev/345ec7455b75

New changeset d1da87d8b29c by Benjamin Peterson in branch 'default':
merge 3.5 (bpo-27514)
https://hg.python.org/cpython/rev/d1da87d8b29c