#6378: Capture arbitrary output as a template variable
---------------------------------+--------------------------------------
Reporter: Kenneth Arnold | Owner: Carl Meyer
Type: New feature | Status: new
Component: Template system | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* stage: Accepted => Unreviewed
Comment:
Grrr, reopening a ticket after 9 years without a clear consensus first
being reached is pretty strong. Ideally that would have happened on the
Forum first. (If I were still Fellowing I would re-close and insist on
that.
I'm going to mark this as Unreviewed so the Fellows get to see it,
otherwise there's a danger it just sits here as Accepted.
I'm (on the record as) leaning towards doing something here — it DOES keep
coming up — but it's at least related to the new #35535, which has a PR,
and for which the Forum discussion linked back here too, so there's some
Triage to be done as to whether there's a separate ticket to be
implemented here too or not.
--
Ticket URL: <https://code.djangoproject.com/ticket/6378#comment:32>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107019111b898c7-403f70bc-acbc-4e16-9ddd-5b282000d7c6-000000%40eu-central-1.amazonses.com.
