<br><br><div class="gmail_quote">On Sun, Jan 10, 2010 at 20:05, Neil Schemenauer <span dir="ltr"><<a href="mailto:nas@arctrix.com">nas@arctrix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Jan 10, 2010 at 07:46:04PM -0800, Brett Cannon wrote:<br>
> On Sun, Jan 10, 2010 at 17:44, Neil Schemenauer <<a href="mailto:nas@arctrix.com">nas@arctrix.com</a>> wrote:<br>
</div><div class="im">> > After the Python 2.7 release, the focus of Python development<br>
> > will be on Python 3. There will continue to be maintainance<br>
> > releases of Python 2.x.<br>
><br>
> No because that suggests new features will be coming to 2.x which is not<br>
> going to happen. If you want to say there will be continual bugfix releases<br>
> for 2.7 as is par the course for Python and that the number of bugfix<br>
> releases might be more than normal then I am okay with that.<br>
<br>
</div>Are you are saying that if someone steps up to merge the Unladen<br>
Swallow features into a 2.8 release and someone also steps up to cut<br>
the release that they will be prevented from doing so?<br>
<br></blockquote><div><br></div><div>I honestly don't know, but it's a possibility just like any other new feature request. If people start taking the carrots we have added to 3.x and backporting them to keep the 2.x series alive you are essentially making the 3.x DOA by negating its benefits which I personally don't agree with.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Also, are you presuming to channel the BDFL or was this dicussed<br>
somewhere other than python-dev?</blockquote><div><br></div><div>This was discussed; see the November 2009 threads. Guido actually suggested ending the 2.x branch at 2.6 until people spoke up about the amount of stuff already backported to 2.7 from 3.x because it was being assumed to be the end of the series to warrant keeping it to help transition to 2.7.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Maybe I'm overreacting but I get<br>
the feeling that the larger and less active segment of the Python<br>
develpment team hasn't been involved in these decisions.<br></blockquote><div><br></div><div>This all came up in November from the 3rd through the 6th (four days) over a ton of email traffic. This was not a snap decision but a heated discussion where even Guido participated that culminated with the decision to stop at 2.7 for the 2.x series; this was not a smoked-filled room decision. I'm sorry if people missed it when they weren't looking, but python-dev is supposed to be the place to watch for this kind of stuff. I don't know how else to bring this stuff to people's attention short of also on python-committers, but developers are basically expected to be on both lists so I don't see where anyone did anything wrong in terms of informing developers.</div>
<div><br></div><div>-Brett</div></div>