If you were already using Python 3, and your code wasn't emitting any deprecation warnings, then it's a fully backwards-compatible change and you can just bump

If you were already using Python 3, and your code wasn't emitting any deprecation warnings, then it's a fully backwards-compatible change and you can just bump the version number in your requirements.txt with no other changes. If your code was emitting deprecation warnings, then you have to fix them before upgrading, but this should be relatively rare and they shouldn't be that hard to fix. If you're still on Python 2, then you have to either migrate to Python 3 or stay on Django 1.11 (which is an LTS release). 1.11 EOL is April 2020, which is the same time as Python 2's EOL, so you were going to have to migrate your codebase by then anyway.