Re: Update django 1.8 project to 2.0 lts

I strongly recommend this approach: My experience is that the best thing to do is to do minor upgrades - 1.8 -> 1.9.x -> 1.10.x -> 1.11.x (where x is the last patched version of each minor version). Further, at the completion of one Django version, I recommend saving a snapshot of your

Re: Update django 1.8 project to 2.0 lts

Hi, My experience is that the best thing to do is to do minor upgrades - 1.8 -> 1.9.x -> 1.10.x -> 1.11.x (where x is the last patched version of each minor version). The reason for updating in this fashion, is that when you start the server on each version, you will get warnings about

Re: Update django 1.8 project to 2.0 lts

django 2.x is not lts, next LTS version is 2.2, as said before. That said, I'd break this into three chunks: migrate 1.8 to 1.11 migrate 2.7 to 3.6 (or 3.7) migrate 1.11 to 2.1 or 2.2, depending on the timing. 2.2 will be out in April 2019, which is seven months from now. I would separate

Re: Update django 1.8 project to 2.0 lts

Django 2.0 Not LTS warning!! the next LTS Django version is 2.2 Cheers On Sun, Sep 23, 2018 at 6:08 PM Mike Dewhirst wrote: > On 23/09/2018 11:15 PM, 'David Brown' via Django users wrote: > > I have a large django project built in 1.8 with about 14 apps and a > large amount of dependencies. >

Re: Update django 1.8 project to 2.0 lts

On 23/09/2018 11:15 PM, 'David Brown' via Django users wrote: 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,

Re: Update django 1.8 project to 2.0 lts

This can take a lot of time but if you're really into this, you can see the the release notes for every version between 1.8 and 2.0 (especially for version 2.0 ) and seek for things you can change in your code that were optimised in the

Re: Update django 1.8 project to 2.0 lts

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 <

Update django 1.8 project to 2.0 lts

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