Re: [python-committers] Steering Council Update for April 2019

2019-04-26 Thread Berker Peksağ
On Fri, Apr 26, 2019 at 11:37 PM Brett Cannon wrote: > Because that repo is private I will say that the last comment on that issue > was exactly a month ago from someone at GitHub saying that they are looking > into this feature request. Thank you, I forgot those links are private. I'll also no

Re: [python-committers] Steering Council Update for April 2019

2019-04-26 Thread Barry Warsaw
On Apr 26, 2019, at 09:12, Berker Peksağ wrote: > I don't think there was a consensus on switching to GitHub Issues last > time it was discussed. The most recent discussion about PEP 581 only > has 12 messages. I think the council is making a premature decision > here. Technically speaking, the

Re: [python-committers] Steering Council Update for April 2019

2019-04-26 Thread Berker Peksağ
On Fri, Apr 26, 2019 at 5:55 PM Guido van Rossum wrote: > - **Issue tracker:** We've discussed PEP 581, "Using GitHub Issues for > CPython" by Mariatta Wijaya. We're in favor of this move, and feel > that the transition should be professionally planned and executed. > In collaboration with

[python-committers] Steering Council Update for April 2019

2019-04-26 Thread Guido van Rossum
I've posted an update from the Steering Council to our repo: https://github.com/python/steering-council/blob/master/updates/2019-04-26_steering-council-update.md I will also link to this on python-dev and on Discourse (discuss.python.org ). For completeness, below is the full text. # Steering C