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

2014-01-17 Thread Terry Reedy
On 1/17/2014 6:27 AM, Nick Coghlan wrote: On 17 Jan 2014 12:03, "Kristján Valur Jónsson" mailto:krist...@ccpgames.com>> 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 even from tho

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

2014-01-17 Thread Nick Coghlan
gt; From: Nick Coghlan [mailto:ncogh...@gmail.com] > Sent: Friday, January 17, 2014 7:51 > To: Kristján Valur Jónsson > Cc: Matthias Klose; python-committers; Martin v. Löwis > > Subject: Re: [python-committers] Updated schedule for Python 3.4 > > > > > On 17 Jan 2014 01:0

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

2014-01-16 Thread Ethan Furman
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

2014-01-16 Thread Georg Brandl
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

2014-01-16 Thread Georg Brandl
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

2014-01-16 Thread 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 accept any improvements for a +2.7 > version even fro

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

2014-01-16 Thread Kristján Valur Jónsson
Klose; python-committers; Martin v. Löwis Subject: Re: [python-committers] Updated schedule for Python 3.4 On 17 Jan 2014 01:02, "Kristján Valur Jónsson" mailto:krist...@ccpgames.com>> wrote: > > The hope is that by not adding features to 2.x, people will flock around 3.x &

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

2014-01-16 Thread 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 contributors who see > > > their patches or feature requests languish on the tracker, and l

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

2014-01-16 Thread Nick Coghlan
pen source *should* work. Regards, Nick. > 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-committers] Update

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

2014-01-16 Thread Serhiy Storchaka
четвер, 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

2014-01-16 Thread Kristján Valur Jónsson
e: [python-committers] Updated schedule for Python 3.4 The hope is that, instead of sitting idle, they actually start working on bugs, and contributing to finishing the release. ___ python-committers mailing list python-committers@python.org https://mail.

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

2014-01-16 Thread Georg Brandl
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

2014-01-16 Thread 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 :) > > > but anyway: > > > > Why not branch 3.4 earl

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

2014-01-16 Thread Georg Brandl
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

2014-01-16 Thread Martin v. Löwis
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

2014-01-16 Thread Nick Coghlan
:python-committers-bounces+kristjan= ccpgames@python.org] On Behalf Of Matthias Klose > Sent: Thursday, January 16, 2014 19:27 > To: python-committers@python.org > Subject: Re: [python-committers] Updated schedule for Python 3.4 > > Am 16.01.2014 12:17, schrieb Kristján Valur Jón

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

2014-01-16 Thread Kristján Valur Jónsson
games@python.org] On Behalf Of Matthias Klose Sent: Thursday, January 16, 2014 19:27 To: python-committers@python.org Subject: 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 raise

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

2014-01-16 Thread Matthias Klose
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

2014-01-16 Thread 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 off at b3. There is no reason to keep all trunk development