Documentation about {% url %} arguments still mentions comma separation
Until 1.2 the {% url %} aditional arguments to the URL was a comma separated list. Now is a space separated list. In the documentation the samples show this new behavior but the text still says: "Additional arguments are optional and should be comma-separated values that will be used as arguments in the URL".
By the way, this change will have a deep impact in existing deployments using Django 1.1. Didn't was a priority to mantain backwards compability? At last this was what is printed here http://docs.djangoproject.com/en/dev/misc/api-stability/
Attachments
(1)
- 13287_docs.diff
(632 bytes
) - added by Gabriel Hurley 15 years ago.
- update reference to "comma-separated values" for url tag to "space-separated values"
Download all attachments as:
.zip
Change History
(9)
| Component: |
Uncategorized → Documentation
|
| Triage Stage: |
Unreviewed → Accepted
|
| Has patch: |
set
|
| Owner: |
changed from nobody to Gabriel Hurley
|
| Status: |
new → assigned
|
| Summary: |
Change in {% url %} arguments break existing code → Documentation about {% url %} arguments still mentions comma separation
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
Replying to rbarberac@gmail.com:
If you are actually reading the docs that accompany the current SVN code and read all the documentation of the
urltag you will see a section located at the bottom marked with Changed in Django Development version. that describes how backwards compatibility is being handled transparently.Ticket #13275 is tracking some additional problems the backward-compatibility code has.
That's an error in the documentation. maybe we shoudl switch this ticket to component: Documentation and correct that sentence to read "Additional arguments are optional and should be space-separated values that will be used as arguments in the URL"