RetroSearch Browse

Wed Feb 21 16:22:44 EST 2018 · https://mail.python.org/pipermail/python-dev/2018-February/152216.html

On Wed, Feb 21, 2018 at 9:53 AM, Brett Cannon <brett at python.org> wrote:

>
>
> On Wed, 21 Feb 2018 at 09:30 Yury Selivanov <yselivanov.ml at 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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180221/44a97708/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2018-February/152216.html below:

[Python-Dev] How is the GitHub workflow working for people?