2016-09-06 10:57 GMT+02:00 Erik Cederstrand <erik+li...@cederstrand.dk>:
> > > Den 6. sep. 2016 kl. 10.20 skrev Lekan Wahab <olamy...@gmail.com>: > > > > Good morning guys. > > I was handed a project at work which was written as far back as 2012. > > Quiet a lot of the packages used in the project are either no longer > being maintained. > > Rebuilding the project from scratch is not option. > > There are way too many moving parts and way too many apps to rebuild it. > > Here are my questions: > > > > 1. In the scenario i am in, what would be the best approach to update > this project or at least get it set up locally? > > First, get the project to run on your local machine with the exact same > package versions as was specified originally. You may have to look in > lib/pythonx.x/site-packages on wherever it was running before, for the > exact versions used, if there is no requirements file. Run the test-suite > for your project and make sure everything is working. > > Second, write more tests! You need lots of tests to verify any future > changes you make to your own and external packages. > > Third, either upgrade external packages to the newest versions, find > alternatives if they are no longer maintained, or maintain the external > package yourself from now on (assuming the license permits, of course). If > the packages depend Django, you may have to do this gradually, as the > newest package versions may no longer support Django 1.4 (see below). > > > 2. Quite a lot of changes have been made between django 1.4 (which was > originally used) and the current version(1.10), what would be the best > version for me to update the project to. > > I mostly use 1.8 anyway. > > Take one minor Django version at a time, reading the upgrade notes along > the way. Update your code to the new way of doing things, and move on to > the next version. That's the supported and recommended way. Even though > that's six versions to upgrade to, it will probably save you time in the > long run instead of upgrading from 1.4 -> 1.10 in one go. > > Happy coding! > > This is probably a requirement - to do each minor upgrade. I don't think it is possible to migrate from 1.4 to 1.10 directly. There are too many deprecations for that. That being said, shouldn't it be possible to migrate from one LTS to another? And if memory serves correctly, 1.4 should be an LTS? Regards, Andréas -- 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/CALXYUb%3Dpj2oHeHc2crphqafwaqktxDmdAx6UcAiaWA9b4ef0EQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
