A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2014-March/133028.html below:

[Python-Dev] Python 4: don't remove anything, don't break backward compatibility

[Python-Dev] Python 4: don't remove anything, don't break backward compatibility [Python-Dev] Python 4: don't remove anything, don't break backward compatibilityVictor Stinner victor.stinner at gmail.com
Mon Mar 10 16:50:12 CET 2014
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.

http://en.wikipedia.org/wiki/Software_versioning#Political_and_cultural_significance_of_version_numbers

Or maybe we should jump directly to Python 5 for asian users and to
follow PHP version!

http://en.wikipedia.org/wiki/Tetraphobia

Victor
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4