#24234: Create Context object in a separate method
-------------------------------------+-------------------------------------
Reporter: AlexHill | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Template system | Version: 1.8alpha1
Severity: Normal | Resolution: wontfix
Keywords: multiple-template- | Triage Stage: Accepted
engines |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by AlexHill):
Hi Tim, Aymeric,
Thanks for your feedback. This is highly specific to DTL, definitely
wouldn't want to document it.
I feel that
* resolving the context argument into a `Context` is a clearly-defined
task suitable for delegation to a function
* it's independently useful (as in my case) outside of `Template.render`
* it existed in standalone form before 1.8 in the form of
`TemplateResponse.resolve_context`, which might be used by others than me.
Putting it in a separate function makes for a straightforward migration.
Would love it if you could be swayed to a +0.
Either way, thanks for the huge job you've done on the multiple template
engine support, this minor inconvenience notwithstanding :)
Cheers
Alex
--
Ticket URL: <https://code.djangoproject.com/ticket/24234#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.7f960ad65ea57181bf740019b6ede7a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
