Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-19 Thread Ronald Oussoren
On 17 Feb 2014, at 00:43, Nick Coghlan wrote: > > On 17 Feb 2014 08:36, "Greg Ewing" wrote: > > > > Larry Hastings wrote: > > > >> 3) We hold off on merging the rest of the Derby patches until after 3.4.0 > >> final ships, then we merge them into the 3.4 maintenance branch so they go > >> in

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-19 Thread Ronald Oussoren
On 20 Feb 2014, at 08:09, Nick Coghlan wrote: > On 20 February 2014 16:42, Ronald Oussoren wrote: >> >> On 17 Feb 2014, at 00:43, Nick Coghlan wrote: >> >>> >>> On 17 Feb 2014 08:36, "Greg Ewing" wrote: Larry Hastings wrote: > 3) We hold off on merging the rest of the

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-19 Thread Nick Coghlan
On 20 February 2014 16:42, Ronald Oussoren wrote: > > On 17 Feb 2014, at 00:43, Nick Coghlan wrote: > >> >> On 17 Feb 2014 08:36, "Greg Ewing" wrote: >> > >> > Larry Hastings wrote: >> > >> >> 3) We hold off on merging the rest of the Derby patches until after 3.4.0 >> >> final ships, then we m

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-17 Thread Nick Coghlan
On 18 Feb 2014 03:37, "Larry Hastings" wrote: > > > On 02/16/2014 04:03 PM, Victor Stinner wrote: >> >> Hi, >> >> The PEP 436 is still a draft and not mentionned in Python 3.4 >> changelog. The PEP proposes to add a DSL, not to modify all modules >> implemented in C. I think that it should be mark

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-17 Thread Larry Hastings
On 02/16/2014 04:03 PM, Victor Stinner wrote: Hi, The PEP 436 is still a draft and not mentionned in Python 3.4 changelog. The PEP proposes to add a DSL, not to modify all modules implemented in C. I think that it should be marked as Final and mentionned in the changelog. http://www.python.org/

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Ethan Furman
On 02/16/2014 10:31 AM, Larry Hastings wrote: I'm very sorry that many people contributed to the Derby expecting their patches to go in to 3.4. This is my fault, for severely miscalculating how the Derby would play out. And I feel awful about it. Don't worry too much. It was a great effor

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Victor Stinner
Hi, The PEP 436 is still a draft and not mentionned in Python 3.4 changelog. The PEP proposes to add a DSL, not to modify all modules implemented in C. I think that it should be marked as Final and mentionned in the changelog. http://www.python.org/dev/peps/pep-0436/ 2014-02-16 19:31 GMT+01:00 La

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Nick Coghlan
On 17 Feb 2014 08:36, "Greg Ewing" wrote: > > Larry Hastings wrote: > >> 3) We hold off on merging the rest of the Derby patches until after 3.4.0 final ships, then we merge them into the 3.4 maintenance branch so they go into 3.4.1. > > > But wouldn't that be introducing a new feature into a > ma

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Greg Ewing
Larry Hastings wrote: 3) We hold off on merging the rest of the Derby patches until after 3.4.0 final ships, then we merge them into the 3.4 maintenance branch so they go into 3.4.1. But wouldn't that be introducing a new feature into a maintenance release? (I.e. some functions that didn't ha

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Georg Brandl
Am 16.02.2014 22:27, schrieb Larry Hastings: > On 02/16/2014 12:36 PM, Serhiy Storchaka wrote: >> 16.02.14 20:31, Larry Hastings написав(ла): >>> 4) We accelerate the schedule for 3.4.1 slightly, so we can get these >>> new signatures into the hands of users sooner. Specifically, I propose >>> we s

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Antoine Pitrou
On Sun, 16 Feb 2014 10:31:21 -0800 Larry Hastings wrote: > > Here's how I propose we move forward. > > 1) We merge the Derby patch for the builtins module into 3.4, simply > because it will "demo well". This still brings potential unstability during the rc phase, so I'd prefer this patch to wa

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Larry Hastings
On 02/16/2014 12:36 PM, Serhiy Storchaka wrote: 16.02.14 20:31, Larry Hastings написав(ла): 4) We accelerate the schedule for 3.4.1 slightly, so we can get these new signatures into the hands of users sooner. Specifically, I propose we ship 3.4.1 two months after 3.4.0. I figure we would releas

Re: [Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Serhiy Storchaka
16.02.14 20:31, Larry Hastings написав(ла): So here we are in the "release candidate" period for 3.4, and we still have all these unmerged Derby patches. And it's simply too late in the release cycle to merge them for 3.4.0. Here's how I propose we move forward. Your plan LGTM (except one que

[Python-Dev] Python 3.4: What to do about the Derby patches

2014-02-16 Thread Larry Hastings
Let's begin with a status update of The Great Argument Clinic Conversion Derby. In retrospect, the Derby was way too ambitious. Once it started I was quickly overwhelmed. Even doing nothing but Derby work, all day every day for two straight weeks, I couldn't keep up with all the bug fixes