Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Django 4.2 and Python 3.11 testing #305

Conversation

Stormheg
Copy link
Contributor

Remove Python 3.7, Django 2.2 and 4.0

Also reworked the Github actions CI matrix a bit with the intend to improve maintainability. See commit message for reasoning.

Most controversial change is not including the compatibility check with the current in-development Django. There is not guarantee on how stable it is and I'd rather not see it included by default in our testing matrix. I feel like CI errors that are caused by a bug in Django are something we would want to avoid, not something to ignore when it occurs.

If there is interest, I'd suggest we set up a separate job that periodically runs the tests against the in-development Django.

Remove Django version from Github CI matrix and only create jobs for
every supported Python. **Reasoning:** not all Django versions are
compatible with every Python. Having to update and/or exclude certain
combinations from the Github matrix is a maintenance overhead.

Failures for a specific Django version can be reviewed by
checking the CI logs.

- Add Django 4.2
- Drop Django 4.0
- Drop Django 2.2

- Add Python 3.11
- Drop Python 3.7
Make it a separate job not run by default when executing tox. The
in-development version of Django can be unstable and cause failures that
are not relevant when contributing.
Reword existing entries for consistency with older entries.
@Stormheg
Copy link
Contributor Author

@Andrew-Chen-Wang as most active co-maintainer, could I kindly ask you to review this PR? Thank you!

Copy link
Contributor

@Andrew-Chen-Wang Andrew-Chen-Wang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine given we have so little tests; as a note, this PR only creates matrices for each python version rather than django-python combo. Less transparency but easier to get up and running.

@Andrew-Chen-Wang
Copy link
Contributor

Not sure why pre-commit is failing. But I also think that's fine.

@Andrew-Chen-Wang Andrew-Chen-Wang merged commit c45757d into django-recaptcha:main Sep 14, 2023
6 of 7 checks passed
@Stormheg Stormheg deleted the chore/django-python-testing-matrix-update branch September 15, 2023 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants