Nick Coghlan wrote:
Terry Reedy wrote:
and this could give some people a mis-impression, most likely negative,
as to the magnitude and nature of the change. Most of the code I am now
writing would, I believe, run with 2.5 except for print(..., file=xxx).
And I know that there was concern for backward compatibility to the
point that some changes were rejected (renaming builtins) or delayed
(deleting duplicate test asserts) for that reason. So I would soften
the statements to "... version of the language that is partially
incompatible with... " and "were made without being bound by backward
compatibility,"
I would agree with Terry - while there are backwards incompatibilities,
they aren't gratuitous.
Then again, Guido does seem to want to discourage people from trying to
target the common subset of the two languages instead of using 2to3 as a
compilation step from the python3 version.
I am not restricting myself to that subset. There simply is an
unchanged core that happens to include what I currently need (except
print, which is isolated in one module). I might need 'except x as y:'
someday and will use it if I do but so far 'except x:' is enough and
back compatible).
tjr
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
