You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hyperkitty (Mailman 3) is a Django project which uses DRF and can work with Django 4.1. It uses DRF 3.13.1 as it is the last released version. This leads to a situation, where DRF 3.13 is used with Django 4.1, which is incompatible, but no warning hints on this incompatibility.
By releasing a version 3.13.2, which states explicitly that it does not work with Django 4.1, indirect users of Django 4.1 will get a hint, when they try to combine incompatible versions.
The text was updated successfully, but these errors were encountered:
dilyanpalauzov
changed the title
Issue 3.13.2 version, stating explicitly that it does not work with Django 4.1
Release 3.13.2 version, stating explicitly that it does not work with Django 4.1
Sep 11, 2022
According to #8599 and #8591 DRF 3.13 does not work with Django 4.1. But https://github.com/encode/django-rest-framework/blob/master/setup.py#L85 says the opposite.
Hyperkitty (Mailman 3) is a Django project which uses DRF and can work with Django 4.1. It uses DRF 3.13.1 as it is the last released version. This leads to a situation, where DRF 3.13 is used with Django 4.1, which is incompatible, but no warning hints on this incompatibility.
By releasing a version 3.13.2, which states explicitly that it does not work with Django 4.1, indirect users of Django 4.1 will get a hint, when they try to combine incompatible versions.
The text was updated successfully, but these errors were encountered: