Benjamin Peterson benjamin at python.org
Thu Jun 27 02:14:32 CEST 2013

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

---

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.



--
Regards,
Benjamin

---

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

---

More information about the python-committers mailing list