[python-committers] cherry picking after rc

2014-10-05 Thread R. David Murray
Larry, saw your discussion on IRC with Georg about what to cherry pick into the release clone before issuing final. IMO you shouldn't cherry pick anything, since I believe there have been *zero* issues opened that said that the RC was broken. IMO the only differences between the last RC and

Re: [python-committers] cherry picking after rc

2014-10-05 Thread Antoine Pitrou
Le 05/10/2014 16:11, R. David Murray a écrit : Larry, saw your discussion on IRC with Georg about what to cherry pick into the release clone before issuing final. IMO you shouldn't cherry pick anything, since I believe there have been *zero* issues opened that said that the RC was broken.

[python-committers] Mark Lawrence

2014-10-05 Thread Benjamin Peterson
BreamoreBoy is back on tracker touching hundreds of issues without adding any new information. This is certainly not the first time. Can we ban him? ___ python-committers mailing list python-committers@python.org

Re: [python-committers] Mark Lawrence

2014-10-05 Thread R. David Murray
On Sun, 05 Oct 2014 14:47:06 -0400, Benjamin Peterson benja...@python.org wrote: On Sun, Oct 5, 2014, at 14:42, Serhiy Storchaka wrote: On 05.10.14 21:15, Benjamin Peterson wrote: BreamoreBoy is back on tracker touching hundreds of issues without adding any new information. This is

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Ned Deily
On Oct 5, 2014, at 12:24 , R. David Murray rdmur...@bitdance.com wrote: It is certainly true that I for one ignore anything with his name on it, because most of the time it is noise and it isn't worth the effort to figure out which ones aren't noise. To me, the main issue is that the noise

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Terry Reedy
On 10/5/2014 2:47 PM, Benjamin Peterson wrote: On Sun, Oct 5, 2014, at 14:42, Serhiy Storchaka wrote: On 05.10.14 21:15, Benjamin Peterson wrote: BreamoreBoy is back on tracker touching hundreds of issues without adding any new information. This is certainly not the first time. Can we ban him?

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Antoine Pitrou
Le 05/10/2014 21:36, Ned Deily a écrit : On Oct 5, 2014, at 12:24 , R. David Murray rdmur...@bitdance.com wrote: It is certainly true that I for one ignore anything with his name on it, because most of the time it is noise and it isn't worth the effort to figure out which ones aren't noise.

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Georg Brandl
On 10/05/2014 09:36 PM, Ned Deily wrote: On Oct 5, 2014, at 12:24 , R. David Murray rdmur...@bitdance.com wrote: It is certainly true that I for one ignore anything with his name on it, because most of the time it is noise and it isn't worth the effort to figure out which ones aren't noise.

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Ned Deily
In article m0sah7$4ci$1...@ger.gmane.org, Georg Brandl g.bra...@gmx.net wrote: On 10/05/2014 09:36 PM, Ned Deily wrote: To me, the main issue is that the noise is not just directed at python committers but also to the python users who have submitted those issues or otherwise following them

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Terry Reedy
On 10/5/2014 3:39 PM, Terry Reedy wrote: I responded on the issue, and will say more privately. I wrote him and tried to communicate three ideas. 1. Closing issues and responding to new messages, while important, are subsidiary to the primary goal of improving Python. 2. We would prefer more

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Georg Brandl
On 10/05/2014 11:01 PM, Ned Deily wrote: In article m0sah7$4ci$1...@ger.gmane.org, Georg Brandl g.bra...@gmx.net wrote: On 10/05/2014 09:36 PM, Ned Deily wrote: To me, the main issue is that the noise is not just directed at python committers but also to the python users who have submitted

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Antoine Pitrou
Le 05/10/2014 23:22, Terry Reedy a écrit : On 10/5/2014 3:39 PM, Terry Reedy wrote: I responded on the issue, and will say more privately. I wrote him and tried to communicate three ideas. 1. Closing issues and responding to new messages, while important, are subsidiary to the primary

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Raymond Hettinger
On Oct 5, 2014, at 1:44 PM, Antoine Pitrou anto...@python.org wrote: Le 05/10/2014 21:02, Terry Reedy a écrit : If you are annoyed, lets discuss specifics and see if we can agree on refined guidelines to give him. It could even be leave Benjamin's issues alone. I'd like him to stop

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Senthil Kumaran
On Sun, Oct 5, 2014 at 6:34 PM, Raymond Hettinger raymond.hettin...@gmail.com wrote: I'm not at all into banning, but it would be nice if Mark's interest could be channelled into something useful. Yes, given that he is reasonable on emails. So requesting him to not just prod/churn issues,

Re: [python-committers] cherry picking after rc

2014-10-05 Thread Larry Hastings
On 10/05/2014 07:11 AM, R. David Murray wrote: Larry, saw your discussion on IRC with Georg about what to cherry pick into the release clone before issuing final. IMO you shouldn't cherry pick anything, since I believe there have been *zero* issues opened that said that the RC was broken.

Re: [python-committers] Mark Lawrence

2014-10-05 Thread Nick Coghlan
On 6 October 2014 07:22, Terry Reedy tjre...@udel.edu wrote: On 10/5/2014 3:39 PM, Terry Reedy wrote: I responded on the issue, and will say more privately. I wrote him and tried to communicate three ideas. 1. Closing issues and responding to new messages, while important, are subsidiary