You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Django 4.2 changed the way storage objects can be defined. A subclassing in the storages.py is not necessary anymore and storages can be defined like so in the settings file instead:
Django-storages "strongly encourages" the switch to this way of defining the storage objects, as written in the documentation.
Rationale
This would be in line with django-storages documentation, simplify the code base by deleting the storages.py file, and would give an easy possibility to add more storage objects.
Solution
If it needs to be changed, I can do it.
The text was updated successfully, but these errors were encountered:
Description
Django 4.2 changed the way storage objects can be defined. A subclassing in the
storages.py
is not necessary anymore and storages can be defined like so in the settings file instead:Django-storages "strongly encourages" the switch to this way of defining the storage objects, as written in the documentation.
Rationale
This would be in line with django-storages documentation, simplify the code base by deleting the storages.py file, and would give an easy possibility to add more storage objects.
Solution
If it needs to be changed, I can do it.
The text was updated successfully, but these errors were encountered: