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

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/133076.html below:

[Python-Dev] Python 4: don't remove anything, don't break backward compatibility

• Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Chris Angelico wrote:
> Terrible idea. Would wreak havoc with comparisons. No. Python 3 is all
> about Unicode, so the right way to proceed is 3.8, 3.9, 3.:, 3.;, 3.<,
> 3.=, 3.>, 3.?, 3.@, 3.A.

And we have all of UCS-4 to play with, so for all
practical purposes the 3.x line can live forever!

The downside is that we'll get endless complaints
from jmfauth about the Flexible Version Number
Representation. :-(

-- 
Greg

• Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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