In recent years Django had multiple major releases, I still remember it as being in 1.x forever. Does somebody know what changed within the Django Community that they break backward compatibility more often?
The deprecation policy[2] is taken very seriously and Django doesn't opt to break things if it can.
Recently there was a very interesting discussion[3] between the Fellows as to whether the version numbering is confusing as this doesn't follow the same pattern as other libraries.
1: https://docs.djangoproject.com/en/dev/internals/release-proc...
2: https://docs.djangoproject.com/en/dev/internals/release-proc...
Related Community Resources
* New goodies in Django 5.0 [blog]: https://fly.io/django-beats/new-goodies-in-django-50/
* What's new in Django 5.0 [video]: https://youtu.be/lPl5Q5gv9G8?feature=shared
* Database generated columns⁽¹⁾: Django & SQLite [blog]: https://www.paulox.net/2023/11/07/database-generated-columns...
* Database generated columns⁽²⁾: Django & PostgreSQL [blog]: https://www.paulox.net/2023/11/24/database-generated-columns...
* Building a Bootstrap styled form in vanilla Django [blog]: https://smithdc.uk/blog/2023/bootstrap_form_in_vanilla_djang...
Curious if anyone has used 2to3 (https://docs.python.org/3/library/2to3.html) for upgrading Python code and can share their experience with it? Would you recommend?
1. https://lp.jetbrains.com/django-developer-survey-2022/
2. https://www.djangoproject.com/download/#supported-versions