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/147039.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`?Matěj Cepl mcepl at cepl.eu
Mon Dec 19 18:40:01 EST 2016
On 2016-12-16, 23:59 GMT, Guido van Rossum wrote:
> No need to get all bent out of shape. My proposal is to simply 
> add a note to the docs recommending against using this.  
> I wouldn't change any code, not even a silent deprecation 
> warning. (Also, read the rest of the thread to learn why this 
> is not the best practice for writing Python 2/3 straddling 
> code.)

Oh, that sounds a way better. Thank you.

Matěj

-- 
https://matej.ceplovi.cz/blog/, Jabber: mcepl at ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
If Patrick Henry thought that taxation without representation was
bad, he should see how bad it is with representation.

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