I suppose you do have good unittest code coverage so do gradual upgrades (which is preferred upgrade path) and read release notes on each version.
2to3 tool is great help to check some obvious issues when upgrading to Python 3. su 23. syysk. 2018 klo 16.57 'David Brown' via Django users < django-users@googlegroups.com> kirjoitti: > I have a large django project built in 1.8 with about 14 apps and a large > amount of dependencies. > > I already have a good idea about how I'm going to update the 2.7 code to > 3.6 or possibly just make it compatible with both, however, I'm not sure > what is the best practice and most efficient way to refactor/upgrade the > django framework to 2.0 from 1.8. > > Bare in mind this thousands of lines of code so efficiency in terms of > work is crucial. > > Thanks in advance for all suggestions! > > -- > 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/d6307d12-8920-434b-b5ec-e9b72c0c3443%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAHn91oc8Edc2T2g5dkJ%2BaqEsaNT1CH%3DtmYjq4TEnmY%3DagHN0VQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
