drop support for python 3.6 and 3.7

[deronnax]

EDIT: as kiendang pointed out, the doctrine is to support the last 5 releases of Django. This means we still support django 3.2, which still supports python 3.6 and 3.7. This will come to an end ~Jun 2024, with the release of Django 5.2, where we won't support django 3.2 anymore.

To hold until the release of Django mid-2024 ,then.

[kiendang]

Could also consider dropping Python 3.7 which has been EOL since June 2023 https://devguide.python.org/versions/

[deronnax]

I discovered DRF still supports django 3.0 and django 3.1, which still support Python 3.6 and 3.7, but this django versions have been EOL for years. Support to django 3.0 and django 3.1 should maybe be removed before removing support for Python 3.6 and 3.7.

[kiendang]

Yup according to #8518 (comment)

We aim each new release to arrive shortly after each Django release.

support for Django 3.0 and 3.1 along with Python 3.6 and 3.7 should be dropped for the next release.

[deronnax]

OK, I will add the removal of python 3.7 in this MR.

[deronnax]

I wonder do I have the blacken-docs error. I do not have the markdown error on my branch. I wonder if the pre-commit tests aren't actually running against master.

[deronnax]

@auvipy may I know why this closing?

[auvipy]

Fixed in main branch 1f2daaf