Set all the python/django version numbers correctly

[jrobichaud]

• remove reference to django 3.2, 4.1, 4.2 (EOL)
• remove python 3.8 (EOL)
• replace pypy-3.10 with pypy-3.11
• add django 5.2rc1 to tox
• make sure tools runs with 3.9
• tell readthedocs to use latest python and ubuntu lts

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.42%. Comparing base (082e5f5) to head (8152b1b).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #863   +/-   ##
=======================================
  Coverage   87.42%   87.42%           
=======================================
  Files          32       32           
  Lines         954      954           
  Branches       76       76           
=======================================
  Hits          834      834           
  Misses        102      102           
  Partials       18       18           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cclauss]

@auvipy Are you OK with dropping Python 3.8 and Django v3.2 support?

Would this fail if we had "5.2" instead of "5.2rc1"?

[jrobichaud]

For the moment yes.

[jrobichaud]

@cclauss when django 5.2 will be officially out we will be able to change 5.2rc1 to 5.2.

Pre-releases have to be exact matches.

[jrobichaud]

In a few days we will be able to make a new PR replacing 5.2rc1 with 5.2.

[jrobichaud]

@cclauss, I let you resolve the conversations if you are satisfied with the fixes. When this one is merged, I have another one I will submit to be merged when django 5.2 will be out officially. (the commit of the future PR ca5fd08)

[cclauss]

Now I see... I usually run these with tox -e py as mentioned at https://docs.github.com/en/actions/use-cases-and-examples/building-and-testing/building-and-testing-python#running-tests-with-tox which gives that flexibility. Without -e py things have to be hard coded.

[auvipy]

Im going to hold this

[jrobichaud]

@auvipy , on hold like waiting for django 5.2 to release?

If so, I will just replace the 5.2rc1 to 5.2 already.

[auvipy]

addressed by #865

[auvipy]

@auvipy , on hold like waiting for django 5.2 to release?

If so, I will just replace the 5.2rc1 to 5.2 already.

we tend to keep bit older versions supported to make the transition easier for legacy projects. thanks for you efforts though. the CI was not fully synced so I have to take care of them.