Home Original page

[python-committers] [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

Xiang Zhang angwerzx at 126.com
Mon May 20 23:34:36 EDT 2019 
Also, Github has just changed its export control. As an international team, does it affect us and PEP581? Maybe better consult the lawyer first?

http://help.github.com/en/articles/github-and-export-controls



| |
Xiang Zhang
|
|
邮箱angwerzx at 126.com
|

签名由 网易邮箱大师 定制

On 05/18/2019 17:12, Senthil Kumaran wrote:


On Wed, May 15, 2019 at 6:44 PM Ezio Melotti <ezio.melotti at gmail.com> wrote:


I share the same concerns: 1) the PEP contains several factual errors.  I pointed this out during
the core-sprints last year and more recently Berker pointed out some
on GitHub: https://github.com/python/peps/pull/1013 ;
4) Berker is/was writing a competing PEP, in order to address the
problems of PEP 581 more effectively since his comments on GitHub
haven't been addressed;



This concerns me a bit. The PEP/announcement acknowledges the work Ezio and Berker. However, it does not express if the PEP had addressed their review comments or had the current maintainers on-board with the proposal. I was of the assumption that if the current maintainers (/domain experts) were on-board, then it will be easier for the rest of us to adopt the new changes.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20190521/d2a98dbd/attachment.html>
More information about the python-committers mailing list