Support for Django 3.2 LTS

[rubendv]

Is your feature request related to a problem? Please describe. In April, Django 2.2 LTS will go out of extended support (see https://www.djangoproject.com/download/, section "Supported Versions"). Django 3.0 and 3.1 are already out of extended support. This means that in April graphite-web will no longer support any version of Django that still receives security updates.

Describe the solution you'd like Add support for Django 3.2 LTS.

Describe alternatives you've considered /

Additional context /

[deniszh]

Hi @rubendv

Yes, that should be done soon. I'm worrying if we can make Django 3.2 work with django-tagging. Migration to django-taggit is possible, but quite hard - and probably not possible for existing installations.

[deniszh]

Ah, we use tagging only for events, in worst case we can just drop events api support.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[deniszh]

Ping

[Roguelazer]

There are a lot of CVEs against django 3.0 now.

CVE-2021-33203 CVE-2021-33571 CVE-2021-45116 CVE-2021-45452 CVE-2021-45115 CVE-2022-22818 CVE-2022-23833 CVE-2022-28346 CVE-2022-28347

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[deniszh]

BTW, looks like current Graphite works with Django 3.2 LTS w/o changes in the code, I just removed couple of deprecated errors.

[deniszh]

See https://github.com/graphite-project/graphite-web/pull/2766

[JohnHay]

Any chance of a release coming out with Django 3.2 or higher support? FreeBSD already removed graphite-web from its ports/packages because of a lack of newer Django support.

[deniszh]

Yes, will finish my PR soon and release new version.

[deniszh]

Django 3.2 support merged to master and 1.1.x branch, release will follow