[Python-Dev] yield without future statement?

[Eric S. Raymond]

Guido van Rossum <guido@python.org>:
> On c.l.py, there's a small discussion going on the necessity of a
> future statement to enable the yield keyword.  The general opinion
> seems to be that the future statement is redundant, since previous
> uses of yield will generally result in a syntax error -- and there
> aren't very many uses of yield in the first place.  The other uses of
> future (nested scopes and division) were needed because these features
> cause *silent* failure -- but with yield, you'd have to work really
> really hard to cause a silent failure.
> 
> Opinions?  I'd love to get rid of this particular future statement.

I think you safely can.  I buy this argument.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

Non-cooperation with evil is as much a duty as cooperation with good.
	-- Mohandas Gandhi