-
Notifications
You must be signed in to change notification settings - Fork 81
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
Upgrade to Django 3.2 LTS #295
Comments
Hi, I'm responsible for Coldfront instance at ICM. I have django version update on schedule soon so maybe you will be interested in PR? ;) We use Kubernetes/Helm for CI/CD and REST to control SLURM so maybe could share some of our other work. At very beginning we had to add Django translation module to CF so it made a braking change but most is still compatible. Coldfront saved us tons of work - great job! Michał |
@mdzik Absolutely! All sounds great. Glad to hear ColdFront is working for you. We would be very interested in any PRs so feel free to send some our way. Upgrading Django, REST Slurm and a translation module all sound awesome and areas we could certainly use some help. Thanks! |
So all is well, now over month in tests + 2 weeks in production. We decided to push for Django 4 and all is well Regarding SSL: Wherever you use python requests etc. you might get (DOI api only?) https://stackoverflow.com/questions/38015537/python-requests-exceptions-sslerror-dh-key-too-small For LDAPS, if you use old ldap server config you could get:
Those are local-environment dependent issues so not really testable. For Django 4 I would need to upgrade url.py ( url() go depracieted) - How far you would like to go? 3 or 4 ;) |
Excellent. Thanks so much for testing.
Curious if you tested v0.9.0? The Changelog here looks like there may be some support for Django 3?
Great, thanks for the info. Agreed these are local-env issues.
We were actually just talking about this and think we'd like to go all the way to Django 4. If you have something going feel free to submit/update the PR and we'll start testing on our end as well. Thanks again. All great stuff. |
Scratch that, just realized Django 4 is not LTS yet. I'm thinking we upgrade to 3.2 LTS first. Then we'll test the jump to 4. |
We're currently on Django 2.2 which ends extended support in April 2022. We should upgrade to the latest 3.2 LTS release.
The text was updated successfully, but these errors were encountered: