# We are planning to update Django version(4.2.17) to curent version in openedx quince

**URL:** <https://discuss.openedx.org/t/we-are-planning-to-update-django-version-4-2-17-to-curent-version-in-openedx-quince/18259>\
**Category:** Community\
**Tags:** how-to, tutor\
**Created:** [January 21, 2026, 9:07am UTC](https://discuss.openedx.org/t/we-are-planning-to-update-django-version-4-2-17-to-curent-version-in-openedx-quince/18259 "2026-01-21T09:07:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Venkata\_Sai\_Durga](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/venkata_sai_durga/32/8808_2.png) [@Venkata\_Sai\_Durga](https://discuss.openedx.org/u/Venkata_Sai_Durga)\
**Post date:** [January 21, 2026, 9:07am UTC](https://discuss.openedx.org/t/we-are-planning-to-update-django-version-4-2-17-to-curent-version-in-openedx-quince/18259/1 "2026-01-21T09:07:26Z")

</div>

is it possible, if possible what is the consequences we will face.

---

<div class="post-metadata">

**Author:** ![discourse\_ai\_spam](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@discourse\_ai\_spam](https://discuss.openedx.org/u/discourse_ai_spam)\
**Post date:** [January 21, 2026, 9:17am UTC](https://discuss.openedx.org/t/we-are-planning-to-update-django-version-4-2-17-to-curent-version-in-openedx-quince/18259/2 "2026-01-21T09:17:32Z")

</div>



---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/openedx/original/2X/e/e0015f89e879bc75925b71fd11133ab15fe98297.png) [@system](https://discuss.openedx.org/u/system)\
**Post date:** [January 21, 2026, 9:18am UTC](https://discuss.openedx.org/t/we-are-planning-to-update-django-version-4-2-17-to-curent-version-in-openedx-quince/18259/3 "2026-01-21T09:18:11Z")

</div>



---

<div class="post-metadata">

**Author:** ![sarina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sarina/32/2308_2.png) [@sarina](https://discuss.openedx.org/u/sarina)\
**Post date:** [January 21, 2026, 2:58pm UTC](https://discuss.openedx.org/t/we-are-planning-to-update-django-version-4-2-17-to-curent-version-in-openedx-quince/18259/4 "2026-01-21T14:58:49Z")

</div>

Hi @Venkata_Sai_Durga - I don’t think this will be possible due to changes/deprecations that were made, but I’ll let @tpayne or @feanil weigh in.

---

<div class="post-metadata">

**Author:** ![feanil](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/feanil/32/37_2.png) [@feanil](https://discuss.openedx.org/u/feanil)\
**Post date:** [January 21, 2026, 3:26pm UTC](https://discuss.openedx.org/t/we-are-planning-to-update-django-version-4-2-17-to-curent-version-in-openedx-quince/18259/5 "2026-01-21T15:26:48Z")

</div>

In order to upgrade from Django 4.2 to 5.2, the biggest issue we ran into was around the migration to the new django storages configuration. The platform uses django storages in a lot of places and you’ll have to migrate them to use the new STORAGES setting instead of the old default storages.

That’s the work that took longest to but there were other smaller stuff, all the work was tracked under [Django 5.2 Upgrade · Issue #339 · openedx/public-engineering · GitHub](https://github.com/openedx/public-engineering/issues/339) if you want to get a sense of the scale.

@Venkata_Sai_Durga what’s preventing you from upgrading to newer release of the platform?