Django: what’s new in 6.0
adamj.eu
Django: what’s new in 6.0
1–10 of 127 posts
Re: Django: what’s new in 6.0
#2Template partials look good, which is one of the key reasons frameworks like React are as good and popular as they are, because you can reuse small segments of code.
Re: Django: what’s new in 6.0
#3Any code or blog written by Adam is worth spending some time on.
It will be interesting to see how the tasks framework develops and expands. I am sad to see the great Django-Q2 lumped in with the awful Celery though.
Re: Django: what’s new in 6.0
#4More discussion: https://news.ycombinator.com/item?id=46153116
Re: Django: what’s new in 6.0
#5Template partials look good, which is one of the key reasons frameworks like React are as good and popular as they are, because you can reuse small segments of code.
React allows for encapsulation of state in a reusable component, its more than just templating.
Re: Django: what’s new in 6.0
#6Template partials look good, which is one of the key reasons frameworks like React are as good and popular as they are, because you can reuse small segments of code.
indeed the vintage templating was a logical bottleneck
Re: Django: what’s new in 6.0
#7[flagged]
Re: Django: what’s new in 6.0
#8Template partials look good, which is one of the key reasons frameworks like React are as good and popular as they are, because you can reuse small segments of code.
indeed the vintage templating was a logical bottleneck
How is it different from include? Just less files from my perspective
Re: Django: what’s new in 6.0
#9Template partials look good, which is one of the key reasons frameworks like React are as good and popular as they are, because you can reuse small segments of code.
They're a neat design. I started using them on my blog the other day as part of trying out Django 6: https://github.com/simonw/simonwillisonblog/blob/faec3532183...
Re: Django: what’s new in 6.0
#10Earlier quoted context omitted.
indeed the vintage templating was a logical bottleneck
How is it different from include? Just less files from my perspective
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...