Drop support for Django 3.2

[ddabble]

Description

Django 3.2's EOL was passed last month (April 1st); see Django's supported versions.

Related Issue

None

Motivation and Context

Removing support for dependencies for which development has stopped.

How Has This Been Tested?

See the GitHub Actions test build.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have run the pre-commit run command to format and lint.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have added my name and/or github handle to AUTHORS.rst
• I have added my change to CHANGES.rst
• All new and existing tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.98%. Comparing base (733f4e0) to head (d163a5c).
Report is 16 commits behind head on master.

❗ Current head d163a5c differs from pull request most recent head 75cc8ce

Please upload reports for the commit 75cc8ce to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1344      +/-   ##
==========================================
+ Coverage   96.83%   96.98%   +0.14%     
==========================================
  Files          24       24              
  Lines        1452     1457       +5     
  Branches      237      240       +3     
==========================================
+ Hits         1406     1413       +7     
  Misses         24       24              
+ Partials       22       20       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ddabble]

@tim-schilling Are you available to review this? I'm planning on opening a release PR after merging this 🙂

[tim-schilling]

I'll to try to make time tomorrow morning, but no promises. Feel free to merge and release without it though!

[ddabble]

Great! No worries if it turns out otherwise :)

I don't have the administrative permissions to merge without a review (assuming that's what you meant), but I can try requesting reviews from some of the other Jazzband members 🙂

[tim-schilling]

Looks good!

If you have time, I'd suggest doing two releases. The first with all of the changes before dropping 3.2. Then another version that drops 3.2. That way anyone using 3.2 still can utilize the latest changes.

Though then again, it's a lot easier to just release it all together 😄

[ddabble]

If you have time, I'd suggest doing two releases. The first with all of the changes before dropping 3.2. Then another version that drops 3.2. That way anyone using 3.2 still can utilize the latest changes.

Nice thinking, let's do that! I'll open a release PR for 3.6.0 before merging this 🙂

We can do 3.7.0 (or 3.6.1? 4.0.0? The version history's relationship with semantic versioning seems slightly inconsistent 😅) with the changes from this PR - though I'm not sure that I see the usefulness of a release that only drops a dependency version used in our CI code..? 🤔 (..apart from removing the asgiref>=3.6 installation requirement, I guess)

[tim-schilling]

Eh, I think minor version changes are fine for both, so 3.7.