[Python-Dev] Helping contributors with chores (do we have to?) (original) (raw)

Victor Stinner victor.stinner at gmail.com
Tue Jun 27 07:50:39 EDT 2017

Small enhancement: I added Python 3.5 support to blurb with the help of Serhiy Storchaka ;-)

Victor

2017-06-25 10:33 GMT+02:00 Antoine Pitrou <solipsis at pitrou.net>:

On Sat, 24 Jun 2017 21:37:46 -0700 Larry Hastings <larry at hastings.org> wrote:

On 06/24/2017 09:14 PM, Serhiy Storchaka wrote: > Not only core developers make PRs for CPython. Since all non-trivial > changes need to be mentioned in Misc/NEWS, blurb becomes a required > tool for all committers.

Well, no. Writing blurb-compatible files becomes a required step for all committers. And blurb makes that easy. But it's pretty easy to write them by hand; that's why we pre-created the "next" directories, and there are instructions in the dev guide. Hmm. If it were so easy, you wouldn't have felt the need to add that functionality to blurb, right? :-) This is touching a more general problem, though. Before GitHub, we (core developers) would take the patch submitted by a contributor, make whatever minor changes were needed (e.g. Misc/NEWS) and push the aggregate ourselves. With GitHub, while it's possible to edit someone else's PR, it's frankly a PITA (I've tried to do it once, I don't want to try a second time unless GitHub makes it massively easier and less footgunning-prone). So we have to rely on contributors to make the PR merge-ready by themselves... which means spending some time guiding them through the oh-so-exciting steps necessary to add the right Misc/NEWS entry, or fix the occasional bit of reStructuredText mis-syntax. Regards Antoine.

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.com

More information about the Python-Dev mailing list