4 ms·
There is an accepted PEP to transition to GitHub issues : https://www.python.org/dev/peps/pep-0581/ https://www.python.org/dev/peps/pep-0581/ . But there is ano
by xtreak29 7y ago
There is an accepted PEP to transition to GitHub issues : https://www.python.org/dev/peps/pep-0581/ https://www.python.org/dev/peps/pep-0581/ . But there is another PEP to keep using roundup to address concerns raised.
- Nicksil 7y ago>But there is another PEP to keep using roundup to address concerns raised. Seems to be this one: www.python.org/dev/peps/pep-0595/ Please correct if I'm wrong.
- xtreak29 7y agoYes, maintainer of the bpo also showed some demos of REST API addition to build other features and gsoc student working on few features like markdown support during this year core dev sprints. There is a separate pep for actual migration https://www.python.org/dev/peps/pep-0588/ https://www.python.org/dev/peps/pep-0588/ . I am not sure when it would take effect or so given the depth of bpo in core dev workflow. There is also an open issue to track workflows that are missing in GitHub but present in bpo : https://github.com/python/core-workflow/issues/359 https://github.com/python/core-workflow/issues/359