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.

Sign up for GitHub

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

Jump to bottom

Migrate to Django 4.2 #31

Open
dehnert opened this issue Oct 16, 2023 · 1 comment
Open

Migrate to Django 4.2 #31

dehnert opened this issue Oct 16, 2023 · 1 comment
Labels
upstream Updates for compatibility with upstream software

Comments

@dehnert
Copy link

dehnert commented Oct 16, 2023

We're currently using Django 3.2. This is okay, but it leaves support in about six months (not that we're great at taking security updates anyway, but still). Django 4.2 is the newest LTS and released half a year ago (https://www.djangoproject.com/download/), so it's past time we migrated.
@dehnert
Copy link
Author

dehnert commented Oct 16, 2023

I haven't tried to migrate or (recently?) read the release notes, so it's certainly conceivable this is just updating setup.py but it might be a lot more work, depending on what has changed.

@dehnert dehnert added the upstream Updates for compatibility with upstream software label Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
upstream Updates for compatibility with upstream software
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dehnert