Switch to Django 5.2?

[aaronoppenheimer]

Now that Django 6 is released, we should consider moving from 4.2 -> 5.2 which is the latest LTS version. We definitely do not want to get several major versions behind.

For fun, I set up an environment, upgraded Django to 5.2 and it all seems to run fine with one exception - running DjangoQ in debug mode, sending a gig announcement email fails when trying to pickle the html 'alternative' part of the email. Whatever, I'm sure it's a small fix to figure out. Looking at the version 5 release notes, it doesn't seem like any of the breaking changes apply to what we're doing..?

What do you all think? @bklang @mmendelson222 @uneasyalliance

[aaronoppenheimer]

I'm thinking more about this - going to Django 5, Bootstrap 5, and a bunch of other stuff that is also long out-of-date.

[aaronoppenheimer]

So... moved a fork to Python 3.14 and latest Django 5.2 - and no changes needed! Just worked. I also updated all of the libraries we use to whatever the latest is. No problems!

Now working on bootstrap 4->5, which has things to fix.

[uneasyalliance]

It sounds like a good idea to me to keep things up to date. For python, I haven't see anything in the code that's likely to change. I suppose it's not surprising if Django and Bootstrap are a little more volatile.

[aaronoppenheimer]

Well, this sat around long enough that we're now up to Django 6. I have forked Go3 into Go4 and updated all the packages and...it just seems to work. All tests pass immediately and in playing with it everything seems to work. Amazing.

One thing I'm still fighting with is django-q and async tasks. Django6 has its own async task framework, but django-q has been udpated to work with django 6 so we don't seem to need to change anything. But the qcluster doesn't work. I'll keep playing with it.

[aaronoppenheimer]

Actually, django-q works fine, I just had the logging turned off. I'm impressed - I didn't have to change a line of code to move to django 6.

I'll keep playing with it, and download a dump of the current live DB to make sure it's working. @bklang not sure what other kinds of verification we'll need to do...?

[bklang]

Are there any DB schema changes associated with the change? If not, I say let's merge this into GO3 and run it for a week or so. If any issues come up, we can be prepared to revert. If everything is as smooth as it seems, we get an easy win.

[aaronoppenheimer]

In the meantime Django has gone to version six. I’m working on a port now. The Django stuff just ran with no changes at all. I updated all of our requirement libraries too. Moving to bootstrap latest version will take just a little bit of time because a few things changed.

…

On Sun, Jun 21, 2026, at 2:22 PM, Ben Klang wrote: *bklang* left a comment (Gig-o-Matic/GO3#694) <#694 (comment)> Are there any DB schema changes associated with the change? If not, I say let's merge this into GO3 and run it for a week or so. If any issues come up, we can be prepared to revert. If everything is as smooth as it seems, we get an easy win. — Reply to this email directly, view it on GitHub <#694?email_source=notifications&email_token=AAWDDNSE4TMECPSTPU7RMDT5BARWDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZWGI4DQMBZGM32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4762880937>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWDDNWQPVPHPSTF25WM2HT5BARWDAVCNFSNUABFKJSXA33TNF2G64TZHMZDEOBZGI2TSMJXHNEXG43VMU5TGNZQGIYTQNRQGI32C5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAWDDNXP64M3NNQOZL4QKHL5BARWDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZWGI4DQMBZGM32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AAWDDNRO6IPFRV3FLQMUQ5T5BARWDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZWGI4DQMBZGM32M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>