Another plus one for Black, without getting too into the weeds. I think the 
time is will save likely outweigh the valid concerns posted here. I've used 
Black extensively on several projects, and much like f-strings, the last 
Pink Floyd album, and broccoli, have found I really like something I didn't 
think I would.

I've gone through the churn of style edits each time I've made a PR to 
Django, despite using flake8. Having an automated tool to avoid that 
back-and-forth time would be a big help. It would also help reduce feelings 
of impostor syndrome; I know I've kicked myself for making basic formatting 
mistakes. Submitting to a project like Django can be intimidating, and this 
would remove some of the intimidation factor. I like to ask with every 
major change, "What does it mean for the newcomer?" Much like the new 2.0 
URL routing syntax, I think this is  a slam-dunk.

While I prefer longer line lengths, I agree we should just stick with 
Black's defaults. Their commentary on the choice of 88 characters is 
compelling: it saves quite a bit of space over PEP-8's 79, but stays 
readable for the greater majority of people. Keeping the code base 
accessible to as many as possible is a big plus. I also find that with 88 
character limits, I can keep three files open on a 16x9 screen in an 
editor, which is a nice editor workspace while working on Django (models 
file, views file, template). While Black may change in the future, I doubt 
the changes would be so large as to cause us to need another "huge commit 
and merge."

Regards,

Tim


-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/3b3f2605-f10e-4262-8547-c854c5cad644%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to