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

Victor Stinner vstinner at redhat.com
Wed May 15 16:41:32 EDT 2019

Le mer. 15 mai 2019 à 20:46, Guido van Rossum <guido at python.org> a écrit :
> But trust me that the SC didn't take this decision lightly. It was unanimous, and we have all thought about this a great deal (and listened to long arguments pro and con). It's also impossible to satisfy everyone -- some people find GitHub unacceptable (I've heard about 1-2 people who refused to create GitHub accounts), but others find bpo unusable (the need to have a bpo account in order to accept the CLA has been brought up repeatedly).

Around me, many people told me that they were awaiting for the PEP 581
to be accepted,. They are now *very kind* that Python issues are
moving to GitHub.

Honestly, I don't understand why people are excited by bug tracker,
for me it's not the most exciting part of development :-) But it seems
like many people were unhappy with Roundup.

At least, I can say that I'm not a big fan of it's UI (maybe too
complex, too many fields) compared to GitHub. I can also understand
that it's annoying for contributor to have to create 2 separated
accounts (bugs.python.org and GitHub) and link them *carefully*
(mistakes are common, you can see that when a contributor waits for
the "CLA signed" label). Sometimes, they are some glitches with
bugs.python.org <=> GitHub integration: some notifications take longer
30 sec or simply never happen.

I understand that GitHub is better to *report* bugs (and maybe to
comment an issue), but maybe worse for bug triage, and that we want to
make sure that it's easier to contribute to Python for "regular

I also know that GitHub isn't perfect and that it will take time to
build a new efficient workflow on top of GitHub.

> A successful migration will take a lot of work, and PEP 588 is where we keep track of tasks to be accomplished. (There are more that haven't made it to that PEP, e.g. the mechanics of the actual move.) We're also hoping to get professional help managing the migration so that not everything relies on volunteers.

That would be great! The migration of the code took something like 2
years and it was a little bit painful for everybody at the beginning.
Having someone paid for that would make the migration shorter and
maybe also smoother.

Night gathers, and now my watch begins. It shall not end until my death.

More information about the Python-Dev mailing list