Any reason in particular for not using github issues (or blockers in achieving this)?
On 21 Feb 2018 21:25, "Guido van Rossum" <gu...@python.org> wrote: > On Wed, Feb 21, 2018 at 9:53 AM, Brett Cannon <br...@python.org> wrote: > >> >> >> On Wed, 21 Feb 2018 at 09:30 Yury Selivanov <yselivanov...@gmail.com> >> wrote: >> >>> FWIW I'm extremely happy with the current workflow. The recent >>> improvements to @miss-islington (kudos to Mariatta!) allowing her to >>> auto-backport PRs and commit them is a big time saver. >>> >>> I can only suggest a couple improvements: >>> >>> 1. Make our bots check the code style—fully enforce PEP 8, lint the >>> code, and detect trailing whitespace on all lines that a PR modifies. >>> >> >> Guido said "no" to this from the outset. >> > > I'm willing to reconsider if there's a good enough tool. Ditto for C code > (or do we already do it for C?). > > FWIW I'm personally hugely happy with the new workflow -- my only regret > is that we're not using GitHub for issue tracking yet. > > -- > --Guido van Rossum (python.org/~guido) > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > jokerjokerer%40gmail.com > >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
