[core 3.70 compat] Django storages config deprecation
Open
Nobody has claimed this yet.
Triage-Needed
- Dominant language
- Python
- Stars
- 71
- Forks
- 91
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
Action for django's storages deprecation:
- Pre or on core-3.70 compat declaration:
- Replace legacy with new (not required)
- Settings on signal-handler (not required)
- On core 3.70 compat declaration: (closes this)
- Use new setting in one CI scenario
See for context:
https://discourse.pulpproject.org/t/action-required-plugins-should-use-djangos-new-storage-config-for-3-70/1866
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 with the core 3.70 compatibility declaration and the CI configuration to identify an existing scenario for this plugin. Update one CI scenario to use Django's new storage setting, then verify that the scenario runs successfully with the core 3.70 compatibility declaration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100