Re: Migrations in Django 1.9: verbose_name and verbose_name_plural

oh, it was you that fixed the warning in django-cms so... thanks again Il giorno lunedì 15 febbraio 2016 22:06:05 UTC+1, Marco Badan ha scritto: > > ok, > > I was able to isolate the url: it's from django cms 3.2.1. > The django cms devs have alrea

Re: Migrations in Django 1.9: verbose_name and verbose_name_plural

On Sunday, February 14, 2016 at 6:37:58 AM UTC-5, Marco Badan wrote: >> >> Hi Tim, >> >> my models (and all my project files) contain only english strings. >> Italian is only on *.po files. >> >> I used git bisect and this is the first comm

Re: Migrations in Django 1.9: verbose_name and verbose_name_plural

ed (once) after migrating to 1.8." but you said you > upgraded from 1.8 to 1.9, so I guess it isn't relevant. > > If you could bisect Django's commit history to find where the behavior > changed, that might yield some insight. > > On Saturday, February 13, 2016 at 8:3

Migrations in Django 1.9: verbose_name and verbose_name_plural

Hello, I've upgraded a project to Django 1.9. I've: LANGUAGE_CODE = 'it' LANGUAGES = (('it', 'Italian'),) With Django 1.8 after running makemigrations I got the no changes detected message. On 1.9 makemigrations creates migrations for all of my apps and all third party apps. I had a look at