#34120: Changing translations of model options and attributes is not detected as
change in making migrations
-------------------------------------+-------------------------------------
     Reporter:  Sajjad Sanikhani     |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Migrations           |                  Version:  4.1
     Severity:  Normal               |               Resolution:
     Keywords:  Translation,         |             Triage Stage:
  Migrations, Models, Locale         |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by Sajjad Sanikhani:

Old description:

> After writing my models with its options, I made migrations.\\
> Then I changed translation of model verbose name in *.po file and
> compiled it.\\
> After that I supposed that executing makemigrations, add new migration
> file that contains new translated verbose name of that model. But it is
> not happened.\\
> This problem is only with gettext_lazy, because this function return
> reference of translation in lazy mode. Thus it is not detected as change.

New description:

 After writing my model with its options, I made migrations.\\
 Then I changed translation of model verbose name in *.po file and compiled
 it.\\
 After that I supposed that executing makemigrations, add new migration
 file that contains new translated verbose name of that model. But it is
 not happened.\\
 This problem is only with gettext_lazy, because this function return
 reference of translation in lazy mode. Thus it is not detected as change.

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34120#comment:1>
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/010701840f6ff97e-9a9dfb17-0088-419a-8a55-c7569536b820-000000%40eu-central-1.amazonses.com.

Reply via email to