Hacker News new | past | comments | ask | show | jobs | submit login

Migrate to python 3. Migrate to Django 3. Migrate to next version of Django Rest Framework.

The cost of maintenance is very high in the Python/Django stack those days!




You should take your car for an oil change regularly. You should go to the dentist every 6 months. And you should consider updating your software dependencies when they announce end-of-life sometime over the next 10 years. It's been 10 years.

https://www.python.org/dev/peps/pep-0373/


Hasn’t Django supported Python 3 for a few years?

https://docs.djangoproject.com/en/1.11/topics/python3/


There's a list of breaking changes in the release notes: https://docs.djangoproject.com/en/dev/releases/3.0/#backward...

It seems that there are very few breaking changes in Django 3 that will be relevant for application developers. Third-party packages poking around in Django's internals might have a slightly harder time, but it still seems very managable.


> The cost of maintenance is very high in the Python/Django stack those days!

True, but the community has done a great job managing this over a long period of time. It's most costly if you haven't been investing along the way.


If you're using python 3 upgrading django should be really easy. DRF and Django haven't had any major breaking changes in a long time.


What are you talking about? Django maintenance policy is clear as day, extremely mature with predictable deprecation cycles with plenty of heads up.

Code is alive and needs maintenance. Period. You cannot expect simultaneously a modern framework with eternal backwards compatibility and security gaps.


Management commands, migrations and ORM from Django can be used with other web frameworks like Falcon, Flask. It can reduce maintenance a lot.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: