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/2016-December/147012.html below:

[Python-Dev] Deprecate `from __future__ import unicode_literals`?

[Python-Dev] Deprecate `from __future__ import unicode_literals`? [Python-Dev] Deprecate `from __future__ import unicode_literals`?Ethan Furman ethan at stoneleaf.us
Fri Dec 16 16:07:01 EST 2016
On 12/16/2016 11:24 AM, Guido van Rossum wrote:

> I am beginning to think that `from __future__ import unicode_literals` does
>  more harm than good. I don't recall exactly why we introduced it, but with
>  the restoration of u"" literals in Python 3.3 we have a much better story
>  for writing straddling code that is unicode-correct.

So cross-version code would be primarily 2.7 and 3.3+ ?  I can live with that.

--
~Ethan~
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