ok, I was able to isolate the url: it's from django cms 3.2.1. The django cms devs have already fixed the warning (*django.conf.urls.patterns() is deprecated and will be removed in Django 1.10*) in develop branch.
I get the unwanted behaviour if I put back the warning using *django.conf.urls.patterns* For reference: the url is here <https://github.com/divio/django-cms/blob/develop/cms/wizards/urls.py> and the related view is WizardCreateView <https://github.com/divio/django-cms/blob/f1e04a539d9df7df19fc4412b8f80f3ea471ea3e/cms/wizards/views.py#L42-L171> . Cheers Marco Il giorno lunedì 15 febbraio 2016 15:31:34 UTC+1, Tim Graham ha scritto: > > Hm, see if you can isolate which URL pattern is causing the issue. Seems > like there might be a module level translation activation that's triggered > when the urlpatterns are processed. > > 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 commit that triggers the >> migrations: >> >> https://github.com/django/django/commit/fe3fc5210f0bb334a679ed420152af1c862c0239 >> >> And ....it's about urls, not migrations. >> I've a few RemovedInDjango110Warnings related to urls due to 3rd parties >> packages (django.conf.urls.patterns() is deprecated, Support for string >> view arguments to url() is deprecated) >> >> >> Il giorno domenica 14 febbraio 2016 03:59:31 UTC+1, Tim Graham ha scritto: >>> >>> The only thing that comes to mind is a paragraph in the 1.8 release >>> notes, "When the leave_locale_alone >>> <https://docs.djangoproject.com/en/1.9/howto/custom-management-commands/#django.core.management.BaseCommand.leave_locale_alone> >>> >>> attribute is False, translations are now deactivated instead of forcing >>> the “en-us” locale. In the case your models contained non-English strings >>> and you counted on English translations to be activated in management >>> commands, this will not happen any longer. It might be that new database >>> migrations are generated (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:35:52 AM UTC-5, Marco Badan wrote: >>>> >>>> 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 the new migration files and I've a lot of >>>> AlterModelOptions and AlterField. >>>> The relevant changes are on verbose_name and verbose_name_plural: >>>> With 1.8 I had untranslated strings (English), with 1.9 I've the >>>> translated strings in Italian. >>>> >>>> (...) >>>> >>>> operations = [ >>>> migrations.AlterModelOptions( >>>> name='category', >>>> options={'verbose_name': 'categoria', >>>> 'verbose_name_plural': 'categorie'}, >>>> ), >>>> migrations.AlterField( >>>> model_name='category', >>>> name='description', >>>> field=models.TextField(verbose_name='descrizione'), >>>> ), >>>> >>>> (...) >>>> >>>> ] >>>> >>>> How can I avoid this behaviour? >>>> >>>> -- 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 https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/93eb650f-27f5-42df-963b-4371bf723b7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
