openedx / openedx/openedx-platform
[Django 4.2 Support]: DEFAULT_FILE_STORAGE and STATICFILES_STORAGE
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
https://django.readthedocs.io/en/stable/internals/deprecation.html
- The DEFAULT_FILE_STORAGE and STATICFILES_STORAGE settings will be removed.
- The django.core.files.storage.get_storage_class() function will be removed.
- from django.core.files.storage import DefaultStorage, get_valid_filename
ImportError: cannot import name 'get_valid_filename' from 'django.core.files.storage'
It has 3 issues together with storages.
https://github.com/django/django/pull/16282 ( django PR )
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating uses of DEFAULT_FILE_STORAGE, STATICFILES_STORAGE, get_storage_class(), and the django.core.files.storage imports in the Open edX codebase. Compare those uses with the Django deprecation page and referenced Django PR; done means the storage integrations no longer depend on the removed settings, function, or import.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100