Re: [Pyunit-interest] comments on PyUnit

[Guido v. R. <gu...@di...>]

> >>>>> "CE" == Chuck Esterbrook <ec...@mi...> writes:
> 
>   CE> Finally, consider the flip side: Is there any reason to give to
>   CE> developers that their assertions MUST be disabled for
>   CE> optimization?
> 
> I don't understand this question.  The definition of optimization for
> Python is "assertions are disabled."(*)  So "assertions must be disabled"
> is tautological.
> 
> Jeremy
> 
> (*) Okay, SET_LINENO instructions are omitted, too, but it is hard to
> imagine anyone having good cause to worry about the performance
> implications of SET_LINENO.

I'll admit that -O is pretty bogus, but I really don't think that
"assertions disabled" and "generating optimized code" should be tied
forever to each other (just because they were once in C).  Once we
have a decent optimizer, I can certainly see providing more control
over code generation options.

--Guido van Rossum (home page: http://www.python.org/~guido/)