On Mon., Oct. 19, 2020, 12:33 Tal Einat, <talei...@gmail.com> wrote: > On Mon, Oct 19, 2020 at 9:24 PM Brett Cannon <br...@python.org> wrote: > >> I think the other way to help is to really lean into automation so >> reviewing is even lighterweight than it is now. Now this can be as simple >> as to remind people when they need to regenerate a file like 'configure' >> via a status check, simply telling people when their PR failed a status >> check, or go as far as try to automate PEP 7/8 stuff. >> >> Or another way to put it is to try and use automation to help make PRs >> more self-service so that there's less required from a human being to do. >> > > A huge +1 from me! > > Besides efficiency, I like that kind of automation because it makes our > checking of these things more consistent and official. Another reason is > that it allows contributors to be more independent in their work, rather > than waiting for someone else to explain what they have to do. > > I've avoided mentioning code style until now since I remembered it being a > bit of a touchy subject a few years ago when I recall it coming up. > Personally I think that the benefits of being able to automate styling and > style checking far outweigh the negatives that were brought up at the time. > Brett, if you'd like to open that can of worms, I'd be willing to help. >
I have too many cans open right now to pop open another one. 😉 -Brett > - Tal >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/SYREVH6WV7LA5JMS5XOA2KRHXF75AUHK/ Code of Conduct: http://python.org/psf/codeofconduct/
