Prepare for merge into Django.

[onno-timmerman]

Hi, think this kind is essential for Django templating. Any timeline if this will merge in Django official? And if so will it merge as such or will it work diffrent. Trying to decide if I already should use it or will have to redo things if you it get merged.

Thanxs for this great plugin!!!

[carltongibson]

Hi @onno-timmerman — Glad you're enjoying it! 👍

There's no rush to try and merge into Django. Better to let the package mature so we can spot any API issues. Current 🎯 is Django 5.2 timeframe which would be released April 2025.

I'd imagine changes would be minimal — a search and replace at most. In any case there'd be clear migration guide.

My advice would be to dive in, and not worry too much about what's a couple of major versions of Django away.

🎁

[carltongibson]

OK, I'll use this as a tracking ticket.

Django 5.1 feature freeze is May 20, 2024. Begin after that.

Todos for a merge to Django:

• Django PR
  • Docs additions, and release notes.
  • Add template tags.
  • Integration partials template loader.
• Migration note here:
  • Remove from INSTALLED_APPS.
  • Remove any manual TEMPLATES setting changes.
  • Remove any {% load partials %} from templates.
  • pip uninstall ...
• Prepare ticket, and possible DEP in case Steering Council vote needed.

[geoffrey-eisenbarth]

Is there a way to track whether or not this merge would happen in Django 5.2? I guess I'm asking if there's discussion regarding this concept in some official Django forum?

Thanks!

[carltongibson]

There's a thread on the Forum, and I'll make a PR against Django after the 5.1 feature freeze