Re: [python-committers] Policy for committing to 2.7
On 27 June 2013 10:14, Benjamin Peterson wrote:
> 2013/6/25 Larry Hastings :
>> 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 | [email protected] | Brisbane, Australia
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Language Summit at EuroPython
Hi, On Wed, Jun 26, 2013 at 4:02 AM, Larry Hastings wrote: > > We didn't have one last year because nobody had anything to say. OK, I asked because the language summit usually happens the day before the beginning of the conference, and I had/have to plan the travel. > If you're > (gentle reader) going to be at EuroPython and think you have something that > needs discussng, please feel free to email me. I don't have any outstanding issues I need to discuss about, even though I would still like to get the regex module included in 3.4. This can probably be discussed informally during the conference if someone is interested. Best Regards, Ezio Melotti > If I get a lot of topics > I'll inquire about getting a room set aside for a couple of hours. > > Cheers, > > > /arry ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
