Backport Python 3.13 support in Django 5.0?

Django Internals
1

As Python 3.13 is approaching, I was wondering if the community of Django packages should expect the Python 3.13 support to be backported to Django 5.0?

I searched and found that the FAQ isn’t advertising support yet, which I fully expect. I also found a mention in the main ticket, which implies that it won’t be the case:

Django 5.1 will be the first version to support Python 3.13, because Django 5.0 will end the mainstream support in August 2024.

I’m starting to look at adding Python 3.13 to the CI of a few Django packages and was wondering how to build the matrix: should the community test Python 3.13 with Django 5.1+ only? Or is backporting support to Django 5.0 an acceptable level of maintenance effort, that it might be added?

I appreciate that it may be too soon to answer yes to a backport but if the answer is already no, the community can plan around that. Might make the CI matrixes a bit more complicated, but that’s probably manageable.

2

Hello @browniebroke!

You have found the correct and updated documentation: Django 5.1 will be the first to support 3.13 and Django 5.0 would not officially support it. The reason is that Django 5.0 has reached the end of mainstream support when 5.1 was released (announcement here) and it will only receive security and data loss fixes.

I hope that answers your inquiry!

4 Likes