[Python-Dev] PEP 407: New release cycle and introducing long-term support versions
solipsis at pitrou.net
Wed Jan 18 00:20:06 CET 2012
On Wed, 18 Jan 2012 10:04:19 +1100
Matt Joiner <anacrolix at 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.
More information about the Python-Dev