A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] Should we move to replace re with regex? [Python-Dev] Should we move to replace re with regex?Brian Curtin brian.curtin at gmail.com
Sat Aug 27 18:53:13 CEST 2011
On Sat, Aug 27, 2011 at 11:48, Dan Stromberg <drsalists at gmail.com> wrote:
>
> 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?
>

It's in the first paragraph.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20110827/843204df/attachment.html>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4