#Django 3 latest version install

that means that, in 2 different terminals you can run 2.7 and 3.x against the same unittest(s).

#Django 3 latest version install

if you have a file-based, git repo, you can point each venv at the same codeline with a pip install -e.Leverage git (or whatever scm you use) and virtualenv. You could always install 3.8 and try a pip install of your requirements.txt by itself, for example.

Which minor version of Python 3.x to start with?īest to consider all angles, such as the availability of your 3rd party libs, support from your CI/devops suite and availability on your chosen server OS images. There's probably a good number of pre-2.x compatibility shims on 1.11 and you'll be getting its 2.x deprecation warnings. So I would move to the latest and greatest 1.11 that way you're already providing some value to your 2.7 users. My criteria here is that Django migrations can be fairly involved (and actually require more thinking than 2=>3 work). Which minor version of Django to start with? if possible, try to gradually merge your changes to the 2.7 production branches and keep your 3.x porting code up to date with prod changes.start with the lowest level code, like utility libraries, that you have test suites for.start early, don't over analyze, but avoid the big bang approach.first Python 3.x, then only later Django 2.x which doesn't run on 2.7.don't use any 3.x specific features, like f-strings.Python 2.7 is your escape pod, until you pull the trigger on 3.x I thought I'd add a bit to the strategy advocated by Wim's answer - get the appropriate version of Django working on both 2.7 and 3.x first - and outline some tactics that worked for me.