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

Django 4.2 #1938

Merged
merged 8 commits into from
Jul 30, 2024
Merged

Django 4.2 #1938

merged 8 commits into from
Jul 30, 2024

Conversation

longhotsummer
Copy link
Contributor

@longhotsummer longhotsummer commented Jul 26, 2024

django 4.2 and python 3.10

i'm going with python 3.10 for now because that's what I've been running locally and it's only EOL in 2026 (see here), so the possible breakage is minimal.

I'm going with django 4.2 for because that's the current long-term support version, until 5.2 comes out.

@longhotsummer longhotsummer marked this pull request as ready for review July 26, 2024 13:37
goose-life
goose-life previously approved these changes Jul 26, 2024
@longhotsummer
Copy link
Contributor Author

This deploys cleanly and is good to go.

After merging this, developers will need to clear their virtualenvs and re-create them from scratch.

Copy link
Contributor

@actlikewill actlikewill left a comment

Choose a reason for hiding this comment

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

works okay on my end

@longhotsummer longhotsummer merged commit f532642 into main Jul 30, 2024
8 checks passed
@longhotsummer longhotsummer deleted the django-4.2 branch July 30, 2024 08:08
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.

3 participants