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 eric.araujo
Recipients docs@python, eric.araujo, flub, moshez, r.david.murray, terry.reedy
Date 2010-09-08.00:49:53
SpamBayes Score 2.5321134e-11
Marked as misclassified No
Message-id <1283906996.33.0.0622228061386.issue9608@psf.upfronthosting.co.za>
In-reply-to
Content
Your rewrite makes the text much clearer in my opinion. Here are some nits for you to grind, cheers :)

1) I’d say “using a bare ``except:``” and maybe add an index entry for “bare except” referring to that section, to make indexing and maybe googling find this.

2) To make the bad examples clearer, I would remove the second inline comment (“will be changed as soon as we run it”). The wording is confusing: Does that mean the code will be changed by Python at runtime? The text after this code example is clear enough, this comment doesn’t help.

3) “except catches all errors, including GeneratorExit which is not even an error”: Isn’t this confusing for beginners?
History
Date User Action Args
2010-09-08 00:49:56eric.araujosetrecipients: + eric.araujo, moshez, terry.reedy, flub, r.david.murray, docs@python
2010-09-08 00:49:56eric.araujosetmessageid: <1283906996.33.0.0622228061386.issue9608@psf.upfronthosting.co.za>
2010-09-08 00:49:54eric.araujolinkissue9608 messages
2010-09-08 00:49:53eric.araujocreate