<br><div class="gmail_quote">On Sat, Aug 27, 2011 at 9:19 AM, Guido van Rossum <span dir="ltr"><<a href="mailto:guido@python.org">guido@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Fri, Aug 26, 2011 at 11:01 PM, Dan Stromberg <<a href="mailto:drsalists@gmail.com">drsalists@gmail.com</a>> wrote:<br>
[Steven]<br>
<div class="im">>> Have then been any __future__ features that were added provisionally?<br>
><br>
> I can't either, but ISTR hearing that from __future__ import was started<br>
> with such an intent. Irrespective, it's hard to import something from<br>
> "future" without at least suspecting that you're on the bleeding edge.<br>
<br>
</div>No, this was not the intent of __future__. The intent is that a<br>
feature is desirable but also backwards incompatible (e.g. introduces<br>
a new keyword) so that for 1 (sometimes more) releases we require the<br>
users to use the __future__ import.<br>
<br>
There was never any intent to use __future__ for experimental<br>
features. If we want that maybe we could have from __experimental__<br>
import <whatever>.<br>
<br></blockquote><div>OK. So what -is- the purpose of from __future__ import?<br> <br></div></div><br>