On Feb 21, 2018, at 13:22, Guido van Rossum <gu...@python.org> wrote: > > I'm willing to reconsider if there's a good enough tool. Ditto for C code (or > do we already do it for C?).
For Python code, flake8 --possibly with our own custom plugins— is the way to go. It would probably take some kind of ratchet or transition period before all of the stdlib were compliant. We’d have to be careful of the inevitable raft of PRs to fix things, which may distract from actual bug fixes and improvements. OTOH, that would be another external dependency pulled in for core Python development. > FWIW I'm personally hugely happy with the new workflow -- my only regret is > that we're not using GitHub for issue tracking yet. I’m very happy with the workflow too, and Mariatta’s and others work has been hugely important in making things work so well. I still miss my “commit when CI completes” button, but oh well. As for the bug tracker, I still do like Roundup, and we have a huge investment in it, not just in resources expended to make it rock, but also in all the history in it and everything that integrates with it. I wouldn’t stop anybody who’s motivated to spearhead a move to GH issues, but I also don’t think that can be taken up lightly. Just look at the vast amount of work Brett and others had to do to migrate code hosting. It would be nice to have integrated reviews and issues (e.g. for auto-closing perhaps), but I also honestly don’t miss much with the current suite of tools. Cheers, -Barry
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ 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
