Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Terry Reedy
On 1/25/2014 9:54 AM, Dirkjan Ochtman wrote: On Sat, Jan 25, 2014 at 2:49 PM, Eli Bendersky wrote: Interesting. Chromium has something kind-of similar, named "commit queue", for developers without actual commit access. Once they get an LGTM, the thing rolls automatically. In fact, core develope

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Terry Reedy
On 1/25/2014 2:55 PM, Antoine Pitrou wrote: On sam., 2014-01-25 at 06:35 -0800, Eli Bendersky wrote: On Sat, Jan 25, 2014 at 6:14 AM, R. David Murray wrote: On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky wrote: > do the latter in Python, which carries a problem we

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Jesus Cea
On 25/01/14 19:33, Ethan Furman wrote: > On 01/25/2014 07:40 AM, Nick Coghlan wrote: >> >> Basically, I suggest implementing the current bug fixes & minor >> features AC patch you're working on, and then calling it done >> for 3.4, with only outright bugs in existing conversions to be >> fixed be

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Antoine Pitrou
On sam., 2014-01-25 at 06:35 -0800, Eli Bendersky wrote: > On Sat, Jan 25, 2014 at 6:14 AM, R. David Murray > wrote: > On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky > wrote: > > do the latter in Python, which carries a problem we'll > probably need to >

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Ethan Furman
On 01/25/2014 07:40 AM, Nick Coghlan wrote: Basically, I suggest implementing the current bug fixes & minor features AC patch you're working on, and then calling it done for 3.4, with only outright bugs in existing conversions to be fixed before 3.5. [...] I think an extra beta is still a good

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Antoine Pitrou
On sam., 2014-01-25 at 17:14 +0100, Antoine Pitrou wrote: > On dim., 2014-01-26 at 01:40 +1000, Nick Coghlan wrote: > > I think an extra beta is still a good idea, though - I'd like to get > > at least the builtins that are already supported converted, since that > > clearly demonstrates the benefi

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Eli Bendersky
On Sat, Jan 25, 2014 at 7:13 AM, R. David Murray wrote: > On Sat, 25 Jan 2014 06:59:19 -0800, Eli Bendersky > wrote: > > On Sat, Jan 25, 2014 at 6:54 AM, Dirkjan Ochtman > wrote: > > > > > On Sat, Jan 25, 2014 at 2:49 PM, Eli Bendersky > wrote: > > > > Interesting. Chromium has something kind-o

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Antoine Pitrou
On dim., 2014-01-26 at 01:40 +1000, Nick Coghlan wrote: > I think an extra beta is still a good idea, though - I'd like to get > at least the builtins that are already supported converted, since that > clearly demonstrates the benefits the tool is designed to bring in > reducing the discrepancies

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Stefan Krah
Larry Hastings wrote: > Please vote for either "continue the Derby" (which also means slipping the > schedule and adding a fourth beta) or "stop the Derby". I think releasing 3.4 on time is more important than adding internal changes that most people won't see at all. So I vote for releasing acc

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Nick Coghlan
On 25 January 2014 23:49, Larry Hastings wrote: > On 01/25/2014 05:35 AM, Antoine Pitrou wrote: > > Stop the Derby. We needn't convert everything for 3.4 (I didn't even > know that was your goal). > > > Converting everything was my goal at one point. At this point it is nowhere > near viable, not

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread R. David Murray
On Sat, 25 Jan 2014 06:59:19 -0800, Eli Bendersky wrote: > On Sat, Jan 25, 2014 at 6:54 AM, Dirkjan Ochtman wrote: > > > On Sat, Jan 25, 2014 at 2:49 PM, Eli Bendersky wrote: > > > Interesting. Chromium has something kind-of similar, named "commit > > queue", > > > for developers without actual

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Donald Stufft
On Jan 25, 2014, at 10:09 AM, R. David Murray wrote: > On Sat, 25 Jan 2014 06:35:59 -0800, Eli Bendersky wrote: >> On Sat, Jan 25, 2014 at 6:14 AM, R. David Murray >> wrote: >> >>> On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky >>> wrote: do the latter in Python, which carries a prob

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread R. David Murray
On Sat, 25 Jan 2014 06:35:59 -0800, Eli Bendersky wrote: > On Sat, Jan 25, 2014 at 6:14 AM, R. David Murray wrote: > > > On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky > > wrote: > > > do the latter in Python, which carries a problem we'll probably need to > > > resolve first - how to know th

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Eli Bendersky
On Sat, Jan 25, 2014 at 6:54 AM, Dirkjan Ochtman wrote: > On Sat, Jan 25, 2014 at 2:49 PM, Eli Bendersky wrote: > > Interesting. Chromium has something kind-of similar, named "commit > queue", > > for developers without actual commit access. Once they get an LGTM, the > > thing rolls automatical

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Dirkjan Ochtman
On Sat, Jan 25, 2014 at 2:49 PM, Eli Bendersky wrote: > Interesting. Chromium has something kind-of similar, named "commit queue", > for developers without actual commit access. Once they get an LGTM, the > thing rolls automatically. In fact, core developers often find it useful too > because the

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Eli Bendersky
On Sat, Jan 25, 2014 at 6:14 AM, R. David Murray wrote: > On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky > wrote: > > do the latter in Python, which carries a problem we'll probably need to > > resolve first - how to know that the bots are green enough. That really > > needs human attention. >

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread R. David Murray
On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky wrote: > do the latter in Python, which carries a problem we'll probably need to > resolve first - how to know that the bots are green enough. That really > needs human attention. By "that needs human attention", do you mean: dealing with the rema

Re: [python-committers] PEP 462: Workflow automation for CPython

2014-01-25 Thread Eli Bendersky
Interesting. Chromium has something kind-of similar, named "commit queue", for developers without actual commit access. Once they get an LGTM, the thing rolls automatically. In fact, core developers often find it useful too because the Chromium tree is sometimes closed ("red"). We don't really do t

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Larry Hastings
On 01/25/2014 05:35 AM, Antoine Pitrou wrote: Stop the Derby. We needn't convert everything for 3.4 (I didn't even know that was your goal). Converting everything was my goal at one point. At this point it is nowhere near viable, not the least because there simply isn't enough time. As disc

Re: [python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Antoine Pitrou
On sam., 2014-01-25 at 05:09 -0800, Larry Hastings wrote: > > Please vote for either "continue the Derby" (which also means slipping > the schedule and adding a fourth beta) or "stop the Derby". Stop the Derby. We needn't convert everything for 3.4 (I didn't even know that was your goal). Regard

[python-committers] Status of the Derby, and request for another slip

2014-01-25 Thread Larry Hastings
The Great Argument Clinic Conversion Derby has been underway for about 2.5 weeks. Here's a status update. I'll try to keep this short. It's taking a lot longer than I expected it to. This has been due to * bugs and flaws in Argument Clinic itself (a "flaw" is an "I didn't foresee that" de