RetroSearch Browse

Wed Jan 15 13:35:00 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-January/131618.html

On Wed, 15 Jan 2014 13:22:44 +0100
"Martin v. Löwis" <martin at v.loewis.de> wrote:
> Am 12.01.14 18:39, schrieb Nachshon David Armon:
> >>> I propose that this new version of python use the python 3 unicode model.
> >>> As the version of python will be fully compatible with both python 2 and
> >>> with python 3 but NOT necsesarily with all existing code in either. It is
> >>> designed as a porting tool only.
> 
> I don't think that it is possible to write an interpreter that is fully
> compatible for all it accepts. Would you think that the program
> 
> print(repr(2**80).endswith("L"))
> 
> is in the subset that should be supported by both Python 2 and Python 3?
> 
> Notice that it prints "True" in Python 2 and "False" in Python 3.

We probably need an "asciibool" that is both true and false.

(for some value of "we" ;-))

Regards

Antoine.

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

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

[Python-Dev] Common subset of python 2 and python 3