#2445: [patch] allow callable values for limit_choices_to
-------------------------------------+-------------------------------------
Reporter: michael@… | Owner: Tim
Type: New feature | Graham <timograham@…>
Component: Core (Other) | Status: closed
Severity: Normal | Version: master
Keywords: sprint2013 | Resolution: fixed
Has patch: 1 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by adamsc64):
I know some people make the `request` available in thread local storage
using middleware (see http://stackoverflow.com/questions/1057252/how-do-i
-access-the-request-object-or-any-other-variable-in-a-forms-clean-
met#answer-1057418). This effectively hacks Django to make its behavior
similar to frameworks that make the request object globally available,
such as Flask. Note however that many people believe this pattern is a bad
practice.
--
Ticket URL: <https://code.djangoproject.com/ticket/2445#comment:63>
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/079.de6eeb2422074628f22e27bfaca9ede1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
