Nick Coghlan ncoghlan at gmail.com
Thu Jun 27 10:52:36 CEST 2013

• Previous message: [python-committers] Policy for committing to 2.7
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 27 June 2013 10:14, Benjamin Peterson <benjamin at python.org> wrote:
> 2013/6/25 Larry Hastings <larry at hastings.org>:
>> I'm not questioning the decision--I'm asking, what is the heuristic I can
>> apply in the future to predict whether or not a change will be accepted into
>> the 2.7 branch.  My current heuristic ("only bad bug fixes") seems to be on
>> the fritz.
>
> I realize everyone wants a nice heuristic. Unfortunately, I don't
> think one exists that explains why every change does or does not land
> in 2.7.

The best one I have is that simplifying cross-version maintenance and
addressing issues that arise due to changes in the underlying
platforms seem to be the two main reasons we do it :)

Cheers,
Nick.

--
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

---

• Previous message: [python-committers] Policy for committing to 2.7
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list