#33476: Formatting Code with Black
-------------------------------------+-------------------------------------
     Reporter:  Mariusz Felisiak     |                    Owner:  Mariusz
         Type:                       |  Felisiak
  Cleanup/optimization               |                   Status:  closed
    Component:  Core (Other)         |                  Version:  4.0
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Carlton Gibson <carlton@…>):

 In [changeset:"b1005c0e4029c23f4e718ce0a7afdfa926c095de" b1005c0]:
 {{{
 #!CommitTicketReference repository=""
 revision="b1005c0e4029c23f4e718ce0a7afdfa926c095de"
 Refs #33476 -- Prevented formatting of .py-tpl files with black by pre-
 commit.

 When using `pre-commit run --all-files`, files explicitly passed to
 black are processed even if they don't match the `include` configuration
 option. For some reason, (only) one of the `*.py-tpl` files is picked up
 by pre-commit. We can avoid this by explicitly excluding certain
 patterns of files for the black hook in the pre-commit configuration.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33476#comment:25>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017f6ef2e073-65993384-331a-4644-98e4-29e56074fa68-000000%40eu-central-1.amazonses.com.

Reply via email to