The real problem with Python 3 - no business case for conversion
Paul Rubin
no.email at nospam.invalid
Wed Jul 7 23:49:42 EDT 2010
Ben Finney <ben+python at benfinney.id.au> writes:
>> On the other hand, the door appears closed for Python 3 adding more
>> stuff that breaks Python 2 code.
>
> What gives you that idea? Can you reference a specific statement from
> the PYthon developers that says that?
It's just logic. As I understand it, future versions of Python 3 are
supposed to not break programs that work under current versions of
Python 3. So any Python 2 program that is a valid Python 3 program
today has to stay valid.
More information about the Python-list
mailing list