In django 5.2, the storage settings were changed to use a STORAGES dictionary. Whilst a welcome change, because django's settings for storage were confusing and weird, this requires a change to our code which needs to be done in a backward compatible way.
The test matrix is our friend.
I'll definitely be doing this work at some point, as my django servers will inexorably march on - but presently, they're all on 4.2 LTS so if anyone needs this sooner rather than later, please either sponsor the issue (get in touch!) or raise a PR!
Supporting Octue
Octue is an Open-Source Software organisation helping you and many others to fight climate change. Providing support for your issues costs us c. 500GBP/day. Might your organisation be in a position to help sponsor this issue?
[ ] We already are (eg via technical partnership or GitHub Sponsors )
[ ] Yes (we'll prioritise this issue, and be in touch)
[ ] No (we'll work on this issue as and when it aligns with our core development activity)
Feature request
Use Case
In django 5.2, the storage settings were changed to use a
STORAGESdictionary. Whilst a welcome change, because django's settings for storage were confusing and weird, this requires a change to our code which needs to be done in a backward compatible way.The test matrix is our friend.
I'll definitely be doing this work at some point, as my django servers will inexorably march on - but presently, they're all on 4.2 LTS so if anyone needs this sooner rather than later, please either sponsor the issue (get in touch!) or raise a PR!
Supporting Octue
Octue is an Open-Source Software organisation helping you and many others to fight climate change. Providing support for your issues costs us c. 500GBP/day. Might your organisation be in a position to help sponsor this issue?