[DEPR]: django-stdimage

Open
#4,650 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
django, python
Domain
backend

Research direction

Search the course-discovery codebase for StdImageField, django-stdimage settings, and related image handling, then review the django-pictures AlterPictureField migration instructions. Replace the existing usage, preserve image files through the data migration, and verify that Celery regenerates responsive variations without data loss.

Written by the indexing model from the issue text.

Description

depr help wanted
Proposal Date

1 July 2025

Ticket Acceptance Date

1 August 2025

Technology Removal Date

15 September 2025

First Open edX Named Release Without This Functionality

Ulmo

Rationale

django-stdimage is no longer maintained and has been archived by its author. Keeping it increases technical debt.

Removal

We propose to remove all usage of django-stdimage and its field StdImageField across the course-discovery codebase.

  • References to StdImageField in models
  • Any settings or code used to configure django-stdimage
Replacement

We will use django-pictures, a modern, responsive, and actively maintained image field library.

It supports:

  • Async image processing via Celery/Dramatiq
  • AVIF/WEBP and multi-size image generation
  • Placeholder and fallbacks
Deprecation

No response

Migration

We'll create a Django data migration using AlterPictureField from django-pictures to convert the field. The migration will retain existing image files and regenerate responsive variations. No data loss is expected.
Migration instructions for django-stdimage github.
Celery will be used to process images asynchronously after migration.

Additional Info
Dominant language
Python
Stars
59
Forks
195
Avg merge
5h 56m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openedx/course-discovery

All issues in openedx/course-discovery

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.