#12075: Add wsgiorg.routing args support
-------------------------------------+-------------------------------------
     Reporter:  Gustavo Narea        |                    Owner:  Anvesh
                                     |  Mishra
         Type:  New feature          |                   Status:  assigned
    Component:  HTTP handling        |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:  WSGI,                |             Triage Stage:  Accepted
  wsgiorg.routing_args               |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Anvesh Mishra):

 Replying to [comment:15 Florian Apolloner]:
 > Two things that come to mind:
 >
 >  * On a technical level I think if this were to be in core it should be
 done via `django/core/handlers/wsgi` where `resolve_request` could be
 overwritten to set `request.environ/META` directly from the returned
 `resolver_match` there (unconditionally, I don't see much gain in a
 middleware and extra setters/getters for such a niche feature).
 >
 >  * On a organizational level I'd like to ask: Do we need this? If
 someone wants it, there is always `request.resolver_match` which can be
 used to copy this data into `environ['wsgiorg.routing_args']` as needed.
 >
 > Given point two I'd like to ask if there are any popular python
 solutions utilizing this, if yes then by all means let's include it. I
 could imagine for instance that sentry's sdk (and others) could be using
 this to get more information about the request (someone would need to
 check this) -- but aside from error reporting not much comes to mind that
 wouldn't be easily worked around manually in code (ie when calling another
 wsgi app from a django view etc…)
 Both points made seem fairly resonable so I would just like to ask what
 would be the future of this ticket? maybe we can have a work around with
 the `resolver_request` as stated in point 1.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/12075#comment:17>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701855e3e8f2c-0e41e084-0472-4dc5-820c-bc241b10716c-000000%40eu-central-1.amazonses.com.

Reply via email to