I'm having a rather confusing scenario regarding makemigrations and language_code:
* I've an app (let's call it myapp) which I'm developing. * myapp relies on the another app (let's call it libapp). * myapp has language_code set to "es-ar". * libapp was developed separately, and has been installed via pip. While developing myapp, whenever I run "makemigrations" a migrations is also created for libapp. The migrations updates all the verbose_name and help_text fields and nothing else. I don't want this, especially since it creates a conflict in the migration graph when I later upgrade libapp. How can I have makemigrations *ignore* the language_code? Also, why does makemigrations create this migration for libapp, but not an equivalent one for django.contrib.admin? I tried looking at things like the admin to see how they avoid this, and found no clues. Thanks, -- Hugo Osvaldo Barrera -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1445230649.556626.413720273.7E8A1A88%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
