Dave Parker schrieb:
On May 28, 3:19 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
Kind of like how this year's program won't work on next year's
Python?
For somebody who has admitted to have only very rudimentary knowledge of
python that's a pretty bold statement, don't you think?
Everthing I know, I learned from Wikipedia. ;)
http://en.wikipedia.org/wiki/Python_(programming_language)#Timeline_and_compatibility
"Like Perl 6, Python 3.0 will break backward compatibility. There is
no requirement that Python 2.x code will run unmodified on Python 3.0.
There are basic changes such as changing the print statement into a
print function (so any use of the print statement will cause the
program to fail) ..."
You should read further:
"""
However, a tool called "2to3" does most of the job of translation,
pointing out areas where it wasn't sure using comments or warnings. Even
in an alpha stage 2to3 appears to be fairly successful at performing the
translation.
"""
And all this is about Py3k- nobody forces anybody to leave python 2.x
series.
I think you should contort yourself a bit wrt backwards compatibility
and stability - given that FT is by no means an established and
productive tool.
Diez
--
http://mail.python.org/mailman/listinfo/python-list
