Hi > 2. there are issues with git history in doing "the great commit".
While I don't have much experience neither in Python/Django nor in git, maybe a view fom "outside" may add something useful to the discussion. I'm just seeing that discussion is separated between on the one hand "black is good. It would help Django, newcomers' entry barrier etc." - and OTOH "black adds a commit to Django that prevents git blame to work properly." So, excuse me to blasphemically ask the question: Isn't that a problem with git? I always asked myself how to properly fix whitespace "bugs" without destroying the "git blame" history. What would in my optinion solve that issue, and hence allow black to be adopted completely in Django without regrets, would be a feature in git to exclude certain commits, or even chunks, from git blame history. This could be done by having a .blameignore file like .gitignore, listing commit hashes that should be ignored in the blame history. So it could be made clear and configurable per project, and even modified after committing - because you can't change git history itself - which code chunks are just "cosmetical" and have not to be treated as real "code". I knot this has nothing to do with Django itself - but really, NOT adopting black because of "git blame" creating wrong results would be the wrong approach IMHO. If you're not saying that I'm completely insane, or git already has this feature, or Ii forgot something, I could try and add a git feature request for that. Even if implemented in 2 years, It could be made sure later that git blame worked correctly backwards then. TL;DR: Use black with Django without compromise, fix git. Christian -- Dr. Christian González https://nerdocs.at -- 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/b689490c-479e-8745-693a-180bdeeed0cd%40nerdocs.at. For more options, visit https://groups.google.com/d/optout.
pEpkey.asc
Description: application/pgp-keys
