News for hackers. Stuff that matters.
Re:Django: What's new in 6.0 – Adam Johnson by agumonkey on Tuesday December 09, 2025 @04:53PM (#46211247)
indeed the vintage templating was a logical bottleneck
Re:Django: What's new in 6.0 – Adam Johnson by f311a on Tuesday December 09, 2025 @05:02PM (#46211347)
How is it different from include? Just less files from my perspective
Re:Django: What's new in 6.0 – Adam Johnson by simonw on Tuesday December 09, 2025 @05:04PM (#46211378)
The "inline partials" feature is neat, means you can use and define a partial at the same time.

The way you can render just a named partial from both the render() shortcut and the include tag is nice too:

https://docs.djangoproject.com/en/6.0/ref/templates/language...

Re:Django: What's new in 6.0 – Adam Johnson by f311a on Tuesday December 09, 2025 @05:16PM (#46211495)
Yeah, but I was doing the same thing 10 years ago with include mixed with extends and blocks. I can just include a file inside a template or render it directly.
Re:Django: What's new in 6.0 – Adam Johnson by chistev on Tuesday December 09, 2025 @05:07PM (#46211408)
I asked the same question
Re:Django: What's new in 6.0 – Adam Johnson by agumonkey on Wednesday December 10, 2025 @12:23AM (#46214371)
you're kinda right, {% partial ... %} vs {% include ... %} is not a big difference, but my mind was vaguely thinking that "includes" have often been seen as large templates, whereas partial have been after the component era with the idea of making small blocks. (my 2 cents)