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 skip.montanaro
Recipients benjamin.peterson, giampaolo.rodola, gpolo, gregory.p.smith, gvanrossum, michael.foord, ncoghlan, pitrou, pupeno, purcell, rhettinger, skip.montanaro
Date 2009-04-02.22:49:44
SpamBayes Score 3.8206713e-07
Marked as misclassified No
Message-id <18901.16644.855391.440766@montanaro.dyndns.org>
In-reply-to <1238700249.8858.33.camel@fsol>
Content
>> You don't, but use of assert statements seems a hell of a lot more
    >> Pythonic to me than all the assert* or fail* method names which I can
    >> never remember.

    Antoine> 1. they are optimized away in "-Oxxx" mode

As far as I can tell for Python itself we never use -O while running unit
tests. 

    Antoine> 2. they don't provide good reporting in case of failure

I've never had a problem with that.  It yields a perfectly useful traceback,
and in the case of the nose package at least, it does the right thing with
it.

In any case, your test machinery will have to catch AssertionError
exceptions anyway.
History
Date User Action Args
2009-04-02 22:49:47skip.montanarosetrecipients: + skip.montanaro, gvanrossum, rhettinger, gregory.p.smith, purcell, ncoghlan, pitrou, giampaolo.rodola, pupeno, benjamin.peterson, gpolo, michael.foord
2009-04-02 22:49:44skip.montanarolinkissue2578 messages
2009-04-02 22:49:44skip.montanarocreate