#31184: URL dispatcher docs should mention path_info
--------------------------------------+------------------------------------
     Reporter:  Roy Smith             |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  Documentation         |                  Version:  master
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by Carlton Gibson):

 Hi Roy, yes, I understand.

 If you have concrete suggestions to make in PRs, I'm happy to look at them
 but your situation is somewhat unusual, and my concern is making things
 more complex for the vast majority of users. Hence, yes, I think the link
 in the URL dispatcher docs is appropriate, but my skepticism about the
 other suggestions.

 In particular, the `STATIC_URL` docs are quiet explicit, and backed by the
 staticfiles app docs which are quite extensive. — I appreciate users still
 find these topics hard (which is because they're complex) so (again) if
 you have a concrete change in mind, please do suggest it.

 At the least, are you up for making the change to the URL dispatcher docs?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31184#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.75959f0e0280de9fee41c960d0c37fcc%40djangoproject.com.

Reply via email to