Hello, On Wed, 18 Jan 2012 10:04:19 +1100 Matt Joiner <anacro...@gmail.com> wrote: > If minor/feature releases are introducing breaking changes perhaps it's > time to adopt accelerated major versioning schedule.
The PEP doesn't propose to accelerate compatibility breakage. So I don't think a change in numbering is required. > For instance there are > breaking ABI changes between 3.0/3.1, and 3.2, and while acceptable for the > early adoption state of Python 3, such changes should normally be reserved > for major versions. Which "breaking ABI changes" are you thinking about? Python doesn't guarantee any A*B*I (as opposed to API), unless you use Py_LIMITED_API which was introduced in 3.2. Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
