On Wed, Mar 30, 2016 at 10:07 AM, Fred Stluka <f...@bristle.com> wrote: > Roger, > > Yeah, I too have a large project that I'll hopefully be migrating > from 1.4 to 1.9 soon. > > It's about 3.5 years worth of work, over 200,000 lines of code > in about 1000 Python source file and Django template files. > > So any tips you come up with will be invaluable. Please post > anything you learn to this thread.
What's prevented me from migrating past 1.6 is that in my apps I import models in the top-level __init__.py, which is no longer supported and now everything fails with "Apps aren't loaded yet". Getting past that will require a major rewrite of the app, so unfortunately we may just stay on 1.6 forever. We just don't have the time or manpower or money for doing it. > ________________________________ > On 3/30/16 9:23 AM, bobhaugen wrote: > > We feel your pain. If you do it, and write down how it goes, we would be > grateful. > https://github.com/valnet/valuenetwork > > On Tuesday, March 29, 2016 at 4:19:59 PM UTC-5, Roger Dunn wrote: >> >> I've inherited a moderately large project written 2 years ago using Django >> 1.4, and wondering if it is worth creating a fresh 1.9 project and porting >> in the old code, or doing an in-place upgrade to 1.9? >> >> I have it running on 1.4 'as is' but if I run python manage.py migrate it >> comes unglued as a lot of stuff has changed since 1.4. -- 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/CACwCsY7c7Nrz4DsroG3Og48F64ZwybO%3DwWGja4eLTdy4pvkXOA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
