Re: [python-committers] possible future PEP discussion format [was: Transfer of power]

2018-07-13 Thread Neil Schemenauer
On 2018-07-13, Ethan Furman wrote: > I stopped reading the PEP 572 threads once it was painfully > obvious that almost all new replies were just saying the same > things over and over and over... Perhaps this can be seen as a kind of economic problem. What is the cost of posting to a PEP discussi

Re: [python-committers] Transfer of power

2018-07-12 Thread Neil Schemenauer
On 2018-07-12, Yury Selivanov wrote: > One way would be to re-elect them every 5 or so years. Essentially, > an N-virate is a dictator-like entity for a few years. Modeling the body after a supreme court seems like a good idea. They don't have to make day-to-day decisions, only settle disputes th

Re: [python-committers] Enabling depreciation warnings feature code cutoff

2017-11-06 Thread Neil Schemenauer
On 2017-11-06, R. David Murray wrote: > I'm curious which ones you are seeing it in? It could be we are > operating in different problem spaces :) In the last few months: Pillow, docutils, dateutil. Some of them could have been PendingDeprecationWarning, I'm not sure. I had that enabled as well

[python-committers] Enabling depreciation warnings feature code cutoff

2017-11-06 Thread Neil Schemenauer
On 2017-11-06, Nick Coghlan wrote: > Gah, seven years on from Python 2.7's release, I still get caught by > that. I'm tempted to propose we reverse that decision and go back to > enabling them by default :P Either enable them by default or make them really easy to enable for development evironment

Re: [python-committers] Pace of change for Python 3.x

2017-01-25 Thread Neil Schemenauer
On 2017-01-25, A.M. Kuchling wrote: > I think this is the next frontier for Python maintenance; we need > full-time core maintainers, no third parties are funding any such > developers, and the PSF doesn't seem interested in pursuing that. IMHO, the PSF should be doing it. I don't know exactly ho

Re: [python-committers] Pace of change for Python 3.x [was: My cavalier and aggressive manner, API] change and bugs introduced for basically zero benefit

2017-01-24 Thread Neil Schemenauer
On 2017-01-24, Victor Stinner wrote: > You should take a look at this old deferred PEP: > https://www.python.org/dev/peps/pep-0407/ Thanks, that's very close to what I was thinking. I would still add that we should be extra careful about incompatible language features until 2.7.x usage has mostly

[python-committers] Pace of change for Python 3.x [was: My cavalier and aggressive manner, API] change and bugs introduced for basically zero benefit

2017-01-24 Thread Neil Schemenauer
On 2017-01-21, Brett Cannon wrote: > So the common theme here regardless of whether you agree with Raymond or > Victor's approach to development is that we are not getting enough code > reviews to go around. To me that's what the systemic issue is that this > email is bringing up. I think there is

Re: [python-committers] Would anyone STOP contributing to Python if we used GitHub?

2015-12-15 Thread Neil Schemenauer
On 2015-12-15, Vinay Sajip wrote: > Brett Cannon python.org> writes: > > Also realize that anyone who says they will walk away will be held to > > their word; if we still choose to switch to GitHub I will expect you to > > no longer contribute to Python and will personally hold you to your word >