Chap con webcan gratis - Updating django

Keeping dependencies updated is crucial to the project's health.

Newer package version close bugs, fix security issues and bring new feature sets from which applications can benefit.

If not, this is certain the first think to consider upgrading, as the support was dropped.

updating django-3

However, this will not be the case if you have upgraded from an older code base.

It appears that the automatic migrations have not used the on_delete argument, as it defaulted to CASCADE.

Instead, it must use a construct that has been introduced with Dajngo 1.9, which uses the app_name defined in the originating app URL configuration.

This means that the ‘my_app.urls’ must define the app_name, like this: This was introduced in Django 1.10 and the methods where still available until 1.11 for Backward compatibilyty.

Fixing on_delete in models or switch from functions to properties in User model will be more complicated.

Of course you can start monkey patching the libraries, but this is not a solution I would recommend, as it will only bring messy stuff to the code and it does not really solve the issue for future applications.

Chances are that the upgrade is much smoother to if the project was built with the 1.11 release, as when it started with 1.8 and got upgraded to 1.11, i describe such a case with migrations bellow.

Please note that I assume you are using Python 3.x.

The best approach would be to find the package repository on Github and make a Fork of it, where you can do all the changes required to make the application run with Django 2.0.

The next step would be to do a pull request with this patch and in an ideal world, you would then use the new release of the package.

This is done after 1.11, but even if not defined, the app will work well as there is no change in the model states.

Tags: , ,