Add support for DRF 3.15, drop Django <4.2 and DRF <3.14

[browniebroke]

Builds on top of #183

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.23%. Comparing base (6b24fae) to head (fc2a87f).
Report is 15 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #186   +/-   ##
=======================================
  Coverage   98.23%   98.23%           
=======================================
  Files           3        3           
  Lines         227      227           
=======================================
  Hits          223      223           
  Misses          4        4           

Flag	Coverage Δ
unittests	98.23% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[ir4y]

@browniebroke Why do you remove mypy checks here and in the next line?

[browniebroke]

My understanding was that DRF stubs (and django-stubs) are now linked to a specific version of DRF and Django. So you should ideally have stubs version == DRF version. This was changed in https://github.com/typeddjango/djangorestframework-stubs/releases/tag/3.14.0 and https://github.com/typeddjango/django-stubs/releases/tag/4.2.0

When you install djangorestframework-stubs==3.15.*, it installs django-stubs==5.0.*, which are for DRF 3.15 and Django 5.0 respectively. Although I just noticed that django-stubs=5.0.x has "partial" support for Django 4.2...

I suppose the problem with running mypy against the wrong versions is that the type check won't find type issues if the stubs are for a different version? What I mean is that if a Django API changed its signature between 4.2 and 5.0, but the stubs used by mypy are for v5, mypy won't detect the problem with 4.2.

[browniebroke]

I can try to add them back if you still want them?

[ir4y]

@ruscoder Could you please have a final look on this pull request and merge?

[ruscoder]

Hi @browniebroke, thanks for the contribution, merged. I'll publish a new release as 0.7.1

[browniebroke]

Thanks!

Since I opened this, Python 3.8 reached EOL, Python 3.13 was released as well as Django 5.1, so I've just opened a couple of follow up PRs to update CI and package metadata:

• Drop support for end-of-life Python 3.8 #187
• Add official support for Django 5.1-5.2 and Python 3.13 #188

Should be pretty similar to this one.