Geek Answers Handbook

Upgrading Django 1.5 to 1.8 in a wild way. Good idea or pretty dumb?

I have an outdated django 1.5 application. The task is to upgrade it to 1.8 in order to enjoy all the advantages of the new version and easily move on to further development.

Since it seems quite difficult to simply upgrade and complete the entire hellish transition. I tried the simplest thing: install the new Django 1.8 and put the models, views and everything in it, and connect them to a copy of the old db. And run it. And it just worked (I did not expect this, I just wanted to see a terrible trace and continue the hard way).

Now let's ask ourselves: Is it a good idea to do it this way or will it bite me after a while when this is not expected? Where are the smells? Or should it work like that?

DB is sqlite3, south is used in development, dir migration is not copied in the new version 1.8, Python 2.7.5, DB without any changes.

Thanks!

+5
source share
1 answer

Everything seems to be in order, there are no problems.

python manage.py makemigrations python manage.py migrate --fake-initial

then I started with application changes and everything just works.

+5
source

More articles:


All Articles