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 meador.inge
Recipients brian.curtin, ezio.melotti, jaime.buelta, lars.gustaebel, meador.inge, r.david.murray
Date 2010-02-28.00:45:53
SpamBayes Score 1.801774e-05
Marked as misclassified No
Message-id <>
> What about changing the exception test to something like what I did in > issue7232.4.diff?

That is definitely more succinct, but Lars' solution provides more information about _why_ the test fails.  IMHO, the descriptiveness is
more important than succinctness.  Especially when debugging a failed
Date User Action Args
2010-02-28 00:45:55meador.ingesetrecipients: + meador.inge, lars.gustaebel, ezio.melotti, r.david.murray, brian.curtin, jaime.buelta
2010-02-28 00:45:55meador.ingesetmessageid: <>
2010-02-28 00:45:53meador.ingelinkissue7232 messages
2010-02-28 00:45:53meador.ingecreate