RetroSearch Browse

Sat Aug 27 18:48:16 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-August/113207.html

On Sat, Aug 27, 2011 at 9:19 AM, Guido van Rossum <guido at python.org> wrote:

> On Fri, Aug 26, 2011 at 11:01 PM, Dan Stromberg <drsalists at gmail.com>
> wrote:
> [Steven]
> >> Have then been any __future__ features that were added provisionally?
> >
> > I can't either, but ISTR hearing that from __future__ import was started
> > with such an intent.  Irrespective, it's hard to import something from
> > "future" without at least suspecting that you're on the bleeding edge.
>
> No, this was not the intent of __future__. The intent is that a
> feature is desirable but also backwards incompatible (e.g. introduces
> a new keyword) so that for 1 (sometimes more) releases we require the
> users to use the __future__ import.
>
> There was never any intent to use __future__ for experimental
> features. If we want that maybe we could have from __experimental__
> import <whatever>.
>
> OK.  So what -is- the purpose of from __future__ import?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20110827/5931b3e9/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-August/113207.html below:

[Python-Dev] Should we move to replace re with regex?