On Wed, Apr 24, 2019 at 9:06 AM Carlton Gibson <[email protected]> wrote:
> On Wednesday, 24 April 2019 08:58:57 UTC+2, Josh Smeaton wrote: >> >> lots of bikeshedding >> > > Yeah. 🙂 > > But we've already got a style guide, so **IF** we can get a YAPF config to > work to that then hopefully the arguments against using a formatter here > would be moot. (Note that **IF** — I only said I'd have a play.) > > Equally, **IF** it's true that the Python community is standardising > around black then, we should join in. But I get the impression that's not a > done deal yet. > > I'm not fussed on the code style. The brain/eye adapts. As I said before, > I would like us to have an auto formatter of some kind. > It's maybe not fair to count all channels-related repositories individually, but when I take a look at the code repositories in the Django organization on Github I see either repositories using only flake8/isort or repositories using black. One could say that the Django organization already is moving towards standardizing on black... The arguments against a particular code style will never stop. In this case it's a big advantage to choose a tool developed by others which does not allow any bikeshedding. I can see why one would want to wait on others to choose a standard tool for the Python community. On the other hand, Django could easily help establish the "obvious way to do it" given its visibility. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANvPqgAzG3YUhOKD4003WF0PwXJ3xKUEAhJYfr-%2BoHuGE8C00w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
