#5034: request.urlconf does not get used in URL template tag
--------------------------------------+-------------------------------------
Reporter: Trey | Owner: nobody
Status: closed | Component: Core framework
Version: SVN | Resolution: duplicate
Keywords: url, urlconf, override | Stage: Design decision
needed
Has_patch: 1 | Needs_docs: 1
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Comment (by Trey <[EMAIL PROTECTED]>):
I didn't think you were saying that, at least not like that. I just don't
see the relationship between this ticket and #3530 that's all. I can see
how they are similar, but the real problem is that request isn't portable
to all pieces of the app. Unless some sort of threadlocal or, if I were in
Java, a singleton style of class were introduced the problem will remain.
Anyway, I guess my point is that the over arching issue is much larger
than either of these two tickets originally and seems like it would be a
major change to the core of django which would require a lot of design
decisions. I would like to see a ticket or topic discussing what the long
term plan is if you know of one. Otherwise, should you or I move my patch
over to #3530 so that I don't have to patch every instance of django?
--
Ticket URL: <http://code.djangoproject.com/ticket/5034#comment:6>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
