[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Ethan Furman ethan at stoneleaf.us
Mon Mar 10 17:20:24 CET 2014
- 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 ]
On 03/10/2014 06:55 AM, Victor Stinner wrote:
What do you think?
I think Python 4.0 will follow Python 3.9. No need to rush things [1].
--
Ethan
[1] The Python 2 line ended early because we had a major paradigm shift with moving to Unicode by default. Unless we experience another major paradigm shift (which would absolutely require backwards incompatible changes), there is no need to end the 3.x line early.
- 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 ]