#23840: Confusing message from makemessages
--------------------------------------+------------------------------------
     Reporter:  takis                 |                    Owner:  iljamaas
         Type:  Bug                   |                   Status:  closed
    Component:  Internationalization  |                  Version:  master
     Severity:  Normal                |               Resolution:  fixed
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  1                     |  Patch needs improvement:  0
Easy pickings:  1                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by Claude Paroz <claude@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"bb4a92d7845878b2ce0c4a5ca154cb4db22f7bad"]:
 {{{
 #!CommitTicketReference repository=""
 revision="bb4a92d7845878b2ce0c4a5ca154cb4db22f7bad"
 Fixed #23840 -- Fixed makemessages find_files method

 Changed the handling of extensions to be used for gettext. Now
 obeying the --extension argument. find_files now only find the
 given or default extensions and puts only these in the
 TranslatableFiles. As a result there are no more confusing messages
 for filetypes (extension) not handled by makemessages.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23840#comment:8>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.dbf512c7f8c508b7f05a84f1e5daa7fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to