Re: [python-committers] Updated schedule for Python 3.4

On 01/16/2014 06:03 PM, � wrote: And while I completely understand that core developers enjoy working in 3 much more, it was decided to not accept any improvements for a +2.7 version [...] You mean, like, new features? Have any new features been put in 2.7 after it hit feature freeze? -- ~

Re: [python-committers] Updated schedule for Python 3.4

Am 17.01.2014 06:34, schrieb Benjamin Peterson: > On Thu, Jan 16, 2014, at 06:03 PM, Kristján Valur Jónsson wrote: >> I never got the impression that this was a matter of funding, Nick. >> And while I completely understand that core developers enjoy working in 3 >> much more, it was decided to not

Re: [python-committers] Updated schedule for Python 3.4

Am 17.01.2014 00:57, schrieb Nick Coghlan: > > On 17 Jan 2014 03:25, "Serhiy Storchaka" > wrote: >> >> четвер, 16-січ-2014 15:03:28 Georg Brandl написано: >> > Am 16.01.2014 14:47, schrieb Antoine Pitrou: >> > > The question is less for us than for occasional contribut

Re: [python-committers] Updated schedule for Python 3.4

On Thu, Jan 16, 2014, at 06:03 PM, Kristján Valur Jónsson wrote: > I never got the impression that this was a matter of funding, Nick. > And while I completely understand that core developers enjoy working in 3 > much more, it was decided to not accept any improvements for a +2.7 > version even fro

Re: [python-committers] Updated schedule for Python 3.4

I never got the impression that this was a matter of funding, Nick. And while I completely understand that core developers enjoy working in 3 much more, it was decided to not accept any improvements for a +2.7 version even from those that would do so voluntarily. This could have be done without

Re: [python-committers] Updated schedule for Python 3.4

On 17 Jan 2014 03:25, "Serhiy Storchaka" wrote: > > четвер, 16-січ-2014 15:03:28 Georg Brandl написано: > > Am 16.01.2014 14:47, schrieb Antoine Pitrou: > > > The question is less for us than for occasional contributors who see > > > their patches or feature requests languish on the tracker, and l

Re: [python-committers] Updated schedule for Python 3.4

On 17 Jan 2014 01:02, "Kristján Valur Jónsson" wrote: > > The hope is that by not adding features to 2.x, people will flock around 3.x en masse :) Very few of us think that way - it's that we think Python 3 is a better language in most ways, and it is certainly much easier and more pleasant to wo

Re: [python-committers] Updated schedule for Python 3.4

четвер, 16-січ-2014 15:03:28 Georg Brandl написано: > Am 16.01.2014 14:47, schrieb Antoine Pitrou: > > The question is less for us than for occasional contributors who see > > their patches or feature requests languish on the tracker, and lose > > interest. > > To be honest, most patches and featu

Re: [python-committers] Updated schedule for Python 3.4

The hope is that by not adding features to 2.x, people will flock around 3.x en masse :) K -Original Message- From: "Martin v. Löwis" [mailto:mar...@v.loewis.de] Sent: 16. janúar 2014 20:19 To: Kristján Valur Jónsson; Matthias Klose; python-committers@python.org Subject: Re: [python-comm

Re: [python-committers] 3.3.4 planning

On Thu, Jan 16, 2014, at 06:30 AM, Georg Brandl wrote: > Hi all, > > I'm planning to release 3.3.4 candidate 1 together with 3.4 beta 3, i.e. > on > the 26th -- and then 3.3.4 final two weeks later if nothing bad comes up. > > As always, there will be one more full 3.3 release after 3.4 final, >

[python-committers] 3.3.4 planning

Hi all, I'm planning to release 3.3.4 candidate 1 together with 3.4 beta 3, i.e. on the 26th -- and then 3.3.4 final two weeks later if nothing bad comes up. As always, there will be one more full 3.3 release after 3.4 final, probably in the May-June timeframe. cheers, Georg ___

Re: [python-committers] Updated schedule for Python 3.4

Am 16.01.2014 14:47, schrieb Antoine Pitrou: > On jeu., 2014-01-16 at 14:22 +0100, Georg Brandl wrote: >> Am 16.01.2014 12:17, schrieb Kristján Valur Jónsson: >> > This is such an obvious question that it probably has been raised before >> >> Oh, only once or twice for every 3.x release so far :)

Re: [python-committers] Updated schedule for Python 3.4

On jeu., 2014-01-16 at 14:22 +0100, Georg Brandl wrote: > Am 16.01.2014 12:17, schrieb Kristján Valur Jónsson: > > This is such an obvious question that it probably has been raised before > > Oh, only once or twice for every 3.x release so far :) > > > but anyway: > > > > Why not branch 3.4 earl

Re: [python-committers] Updated schedule for Python 3.4

Am 16.01.2014 12:17, schrieb Kristján Valur Jónsson: > This is such an obvious question that it probably has been raised before Oh, only once or twice for every 3.x release so far :) > but anyway: > > Why not branch 3.4 earlier than release? That is how big projects are managed > nowadays, you

Re: [python-committers] Updated schedule for Python 3.4

Am 16.01.14 12:38, schrieb Kristján Valur Jónsson: > I suppose different projects have different ways, but I'm actually talking > about commercial projects with which I am somewhat familiar. > Once a project goes into feature freeze, it is branched off so that continued > feature development can

Re: [python-committers] Updated schedule for Python 3.4

On 16 Jan 2014 21:54, "Kristján Valur Jónsson" wrote: > > I suppose different projects have different ways, but I'm actually talking about commercial projects with which I am somewhat familiar. > Once a project goes into feature freeze, it is branched off so that continued feature development can

Re: [python-committers] Updated schedule for Python 3.4

I suppose different projects have different ways, but I'm actually talking about commercial projects with which I am somewhat familiar. Once a project goes into feature freeze, it is branched off so that continued feature development can commence, while Defects are ironed out in the branch. Bugs

Re: [python-committers] Updated schedule for Python 3.4

Am 16.01.2014 12:17, schrieb Kristján Valur Jónsson: > This is such an obvious question that it probably has been raised before, but > anyway: > Why not branch 3.4 earlier than release? That is how big projects are > managed nowadays, you create a staging branch early. > I'd suggest branching it

Re: [python-committers] Updated schedule for Python 3.4

This is such an obvious question that it probably has been raised before, but anyway: Why not branch 3.4 earlier than release? That is how big projects are managed nowadays, you create a staging branch early. I'd suggest branching it off at b3. There is no reason to keep all trunk development