[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Victor Stinner victor.stinner at gmail.com
Mon Mar 10 16:50:12 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 ]
2014-03-10 16:25 GMT+01:00 Stefan Richthofer <Stefan.Richthofer at gmx.de>:
I don't see the point in this discussion. As far as I know, the major version is INTENDED to indicate backward-incompatible changes.
This is not a strict rule. I would like to follow Linux 3 which didn't break the API between Linux 2 and Linux 3.
Even then, there is no need for 4.0; you can just have 3.10, 3.11 etc.
The major version is sometimes seen as the age of a project. I propose to bump Python to version 4 because people understand that Python 4 is much better than Python 3 :-) Firefox changes its major version every 4 months or something like that. I suggest to wait less than 8 years for Python 4.
Or maybe we should jump directly to Python 5 for asian users and to follow PHP version!
http://en.wikipedia.org/wiki/Tetraphobia
Victor
- 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 ]