Skip to content

[DEPR]: DEFAULT_FILE_STORAGE and STATICFILES_STORAGES #37333

Open

Description

@kdmccormick

RFC Start Date

N/A -- Already Accepted

Target Plan Accepted Date

N/A -- Already Accepted

Target Transition Unblocked Date

Immediately -- Transition Already Unblocked

Earliest Breaking Changes Unblocked Date

Python settings: 2025-09-08 (already past)
YAML settings: 2025-10-24 (after Ulmo cut)

Rationale

This is a mandatory part of the django 4.2->5.2 upgrade.

We recently landed this settings change on edx-platform master and operators running on master will need to edit their config accordingly.

Description

These Django settings:

  • DEFAULT_FILE_STORAGE
  • STATICFILES_STORAGE

have been replaced with with:

  • STORAGES

See the django-storages upgrade docs for more details.

For operators using a custom DJANGO_SETTINGS_MODULE

Update your config now. The old settings no longer work.

For operators using a YAML File

We have included a temp backwards compatibility shim so that the old settings are still respected when specified via YAML.

This shim will be removed right after the Ulmo cut (as early as Oct 9) so please update your config in the next month.

Task List

No response

Activity

  1. added
    deprProposal for deprecation & removal per OEP-21
    on Sep 8, 2025
  2. moved this from Draft to Breaking Changes Unblocked in DEPR: Deprecation & Removalon Sep 8, 2025
  3. moved this from Breaking Changes Unblocked to Transition Unblocked in DEPR: Deprecation & Removalon Sep 8, 2025
  4. self-assigned this
    on Sep 8, 2025
  5. kdmccormick commented on Sep 8, 2025

    @kdmccormick
    MemberAuthor

    FYI @pdpinch -- This may affect your instance when you merge in the latest master.

  6. kdmccormick commented on Sep 8, 2025

    @kdmccormick
    MemberAuthor

    For reference, this is how 2U updated their devstack's config to handle this breaking change: edx/devstack#172

  7. jcapphelix commented on Oct 8, 2025

    @jcapphelix

    Is this still planned with same dates as mentioned in DEPR or is this also pushed to Oct 23 ?

  8. kdmccormick commented on Oct 8, 2025

    @kdmccormick
    MemberAuthor

    good question. it's pushed until whenever the Ulmo cut is -- currently, Oct 23rd.

  9. dianakhuang commented on Oct 30, 2025

    @dianakhuang
    Contributor

    @kdmccormick check how credentials handled this and how to write good release notes.

  10. moved this from Transition Unblocked to Breaking Changes Unblocked in DEPR: Deprecation & Removalon Jan 8, 2026
  11. dianakhuang commented on Jan 8, 2026

    @dianakhuang
    Contributor

    Ulmo cut happened, so this is now unblocked. This will be going away with Verawood, so will check back in then.

  12. added theissue type on Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

deprProposal for deprecation & removal per OEP-21

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions