#6603: QuerySet in extra_context should be handled automatically
---------------------------------------------+------------------------------
Reporter: Waldemar Kornewald | Owner: nobody
Status: new | Milestone:
Component: Generic views | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 1 |
---------------------------------------------+------------------------------
Comment (by sunrise):
I'd like to throw my meager weight behind this ticket, despite it being
documented for a good 2 years now (as of [2949]), it's a pretty irritating
issue. Despite being a Django user since before aforementioned changeset,
I still make this mistake (using QuerySets sans lambda within
extra_context) quite often, and I'd like to think that's due more to the
inconsistency aspect and less to my lack of mental conditioning.
[http://www.tagnice.com nike air yeezy]
The patch looks OK to me, although the raw_extra_context argument name
should probably change to extra_context else the code as-is is a little
broken :) I was also going to say that it might work better as an
extension to RequestContext but then realized there's a few spots where
we're operating on a normal dictionary and not a RC instance, so never
mind.
--
Ticket URL: <http://code.djangoproject.com/ticket/6603#comment:8>
Django <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
