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 abbeyj
Recipients abbeyj, collinwinter, jyasskin, pitrou
Date 2009-06-10.03:59:38
SpamBayes Score 2.0208113e-11
Marked as misclassified No
Message-id <1244606385.56.0.541524324574.issue6250@psf.upfronthosting.co.za>
In-reply-to
Content
Python currently emits bytecode for code that is unreachable (e.g.
following a return statement).  This doesn't hurt anything but it takes
up space doing nothing.

This patch attempts to avoid generating any bytecode in this situation.
 There's an optional warning, enabled with the -r command line switch,
which notifies you if any unreachable code is found.  Running
regrtest.py with this switch produces a bit of noise but also revealed
issue6227 which looks like a real bug.
History
Date User Action Args
2009-06-10 03:59:46abbeyjsetrecipients: + abbeyj, collinwinter, pitrou, jyasskin
2009-06-10 03:59:45abbeyjsetmessageid: <1244606385.56.0.541524324574.issue6250@psf.upfronthosting.co.za>
2009-06-10 03:59:42abbeyjlinkissue6250 messages
2009-06-10 03:59:42abbeyjcreate