Re: [python-committers] How to calm down the discussion on the PEP 572?

Ah sorry, results were surprising, so I did more stats including python-ideas. "PEP 572: 662 msg" is now the obvious winner. Congrats Chris Angelico for the new record! python-dev + python-ideas, Jan 2017 - April 2018 : vstinner@apu$ ./parse_mailman_mbox2.py python-dev/* python-ideas/* PEP 572:

Re: [python-committers] How to calm down the discussion on the PEP 572?

> On Apr 26, 2018, at 8:03 AM, Guido van Rossum > wrote: > > The way to calm discussions is to stop responding. Hi Victor, In the gentlest way that I know how, I commend you for considering the impact that emails have on PEP writers especially

Re: [python-committers] How to calm down the discussion on the PEP 572?

2018-04-26 17:13 GMT+02:00 Antoine Pitrou : > Obviously, the issue is less the number of messages per month than the > fact that most of them are about a single proposal :-) Ok, I did statistics on emails with a subject which contains exactly "PEP xxx", since January 2017 to

Re: [python-committers] How to calm down the discussion on the PEP 572?

Obviously, the issue is less the number of messages per month than the fact that most of them are about a single proposal :-) Regards Antoine. Le 26/04/2018 à 17:10, Victor Stinner a écrit : > I computed stats since January 2017: > > 2017-01: Total: 220 msg; avg: 7.6 msg/day; max: 20 msg at

Re: [python-committers] How to calm down the discussion on the PEP 572?

I computed stats since January 2017: 2017-01: Total: 220 msg; avg: 7.6 msg/day; max: 20 msg at 2017-01-18 2017-02: Total: 191 msg; avg: 7.1 msg/day; max: 27 msg at 2017-02-24 2017-03: Total: 240 msg; avg: 8.0 msg/day; max: 20 msg at 2017-03-03 2017-04: Total: 79 msg; avg: 3.0 msg/day; max: 9 msg

Re: [python-committers] How to calm down the discussion on the PEP 572?

The way to calm discussions is to stop responding. On Thu, Apr 26, 2018 at 4:02 AM, Victor Stinner wrote: > Hi, > > Since 2 or 3 years, I saw that that discussions on some PEPs get more > and more emails every year. Maybe because Python became more popular? > Openness is a

Re: [python-committers] Idea: Create subteams?

Ok, maybe asyncio is not a good candidate to experiment. I know that asyncio internals are complex, and asynchronous programming is hard. Sure, the risk of regression in the Documentation is lower :-) But it doesn't mean that we should accept any change in the doc. I already saw people proposing

Re: [python-committers] Idea: Create subteams?

On Thu, Apr 26, 2018 at 10:12 AM Victor Stinner wrote: [..] > I identified 3 obvious subteams: > * Documentation > * IDLE > * asyncio Sorry, asyncio isn't an obvious choice for me. There are not so many low-hanging fruits left in asyncio except improvements to its

[python-committers] Idea: Create subteams?

Hi, While thinking about how to get more contributors onboard, I identified that one bottleneck is building trust. Currently, a vote to promote a contributor as a core dev requires the approval of almost all active core developers, and this list is quite large (50 people? more?). It takes a lot

[python-committers] How to calm down the discussion on the PEP 572?

Hi, Since 2 or 3 years, I saw that that discussions on some PEPs get more and more emails every year. Maybe because Python became more popular? Openness is a Python quality, but shortly, the amount of emails becomes an issue, at least for the author of the PEP. I counted the number of emails per