from __future__ import generators

[David Bolen]

Guido van Rossum <guido at python.org> writes:

> But note that future statements were intended in the first place to
> avoid *silent* breakage -- where existing code suddenly means
> something different.  This was the case (in some rare situations) with
> nested scopes and is clearly the case with division.

It seems to me that the relevant PEPs are pretty well focused on any
"incompatible" change, whether silent or not, and the use of
__future__ to maintain at least one release of no difference in
behavior, except for warnings.  Certainly PEP 236's intent section
highlights this.  And I think that's good policy.

I'd probably prefer that it not only relate to silent breakage, but if
that's the desired intent, it might also be helpful to clarify the
PEPs.

--
-- David
-- 
/-----------------------------------------------------------------------\
 \               David Bolen            \   E-mail: db3l at fitlinxx.com  /
  |             FitLinxx, Inc.            \  Phone: (203) 708-5192    |
 /  860 Canal Street, Stamford, CT  06902   \  Fax: (203) 316-5150     \
\-----------------------------------------------------------------------/