Great, thanks for looking into it! On Wednesday, May 9, 2012 9:27:08 PM UTC-4, Russell Keith-Magee wrote: > > Hi Greg, > > Thanks for the report. From the look of it, the problem is actually > with Django's documentation site, not with the documentation itself. > > If you look at the raw source file for the documentation in 1.4: > > > https://github.com/django/django/blob/stable/1.4.x/docs/ref/templates/builtins.txt#L1096 > > > You'll see that the source for the documentation in 1.4 still has the > future-compatibility warning, and the 'old' syntax. > > This means the problem is with the Djangoproject website; for some > reason, it's showing the trunk documentation for 1.4, rather than the > docs from the actual 1.4 branch. > > This is probably an artefact of our recent move to GitHub; it's taking > a while to get all our ducks back in a row when it comes to things > like the docs that are auto generated out of source. > > I've logged a ticket to track the problem: > > https://code.djangoproject.com/ticket/18293 > > Yours, > Russ Magee %-) > > On Thu, May 10, 2012 at 8:09 AM, Greg Nicholas <greg.nicho...@gmail.com> > wrote: > > Correct me if I'm wrong, but I think 1.4's documentation has jumped the > gun > > in describing the url template tag's syntax. > > > > According to 1.4's documentation: > > > >>> {% url 'path.to.some_view' v1 v2 %} > >> > >> The first argument is a path to a view function in the > >> format package.package.module.function. It can be a quoted literal or > any > >> other context variable. > > > > > > Based on some simple tests I've run, it cannot be a quoted literal. > i.e. {% > > url myapp.views.home %} works, while {% url 'myapp.views.home' %} fails. > > > > This makes complete sense after taking a look at the docs for 1.3. It > > contains a "Forwards compatibility" section that says this quoted view > > behavior will be the standard in 1.5, and until then {% load url from > future > > %} is necessary to enable it, but the 1.4 docs describe the situation as > if > > it is already the standard. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Django users" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/django-users/-/mRBNdd771u8J. > > To post to this group, send email to django-users@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. >
On Wednesday, May 9, 2012 9:27:08 PM UTC-4, Russell Keith-Magee wrote: > > Hi Greg, > > Thanks for the report. From the look of it, the problem is actually > with Django's documentation site, not with the documentation itself. > > If you look at the raw source file for the documentation in 1.4: > > > https://github.com/django/django/blob/stable/1.4.x/docs/ref/templates/builtins.txt#L1096 > > > You'll see that the source for the documentation in 1.4 still has the > future-compatibility warning, and the 'old' syntax. > > This means the problem is with the Djangoproject website; for some > reason, it's showing the trunk documentation for 1.4, rather than the > docs from the actual 1.4 branch. > > This is probably an artefact of our recent move to GitHub; it's taking > a while to get all our ducks back in a row when it comes to things > like the docs that are auto generated out of source. > > I've logged a ticket to track the problem: > > https://code.djangoproject.com/ticket/18293 > > Yours, > Russ Magee %-) > > On Thu, May 10, 2012 at 8:09 AM, Greg Nicholas <greg.nicho...@gmail.com> > wrote: > > Correct me if I'm wrong, but I think 1.4's documentation has jumped the > gun > > in describing the url template tag's syntax. > > > > According to 1.4's documentation: > > > >>> {% url 'path.to.some_view' v1 v2 %} > >> > >> The first argument is a path to a view function in the > >> format package.package.module.function. It can be a quoted literal or > any > >> other context variable. > > > > > > Based on some simple tests I've run, it cannot be a quoted literal. > i.e. {% > > url myapp.views.home %} works, while {% url 'myapp.views.home' %} fails. > > > > This makes complete sense after taking a look at the docs for 1.3. It > > contains a "Forwards compatibility" section that says this quoted view > > behavior will be the standard in 1.5, and until then {% load url from > future > > %} is necessary to enable it, but the 1.4 docs describe the situation as > if > > it is already the standard. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Django users" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/django-users/-/mRBNdd771u8J. > > To post to this group, send email to django-users@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > On Wednesday, May 9, 2012 9:27:08 PM UTC-4, Russell Keith-Magee wrote: > > Hi Greg, > > Thanks for the report. From the look of it, the problem is actually > with Django's documentation site, not with the documentation itself. > > If you look at the raw source file for the documentation in 1.4: > > > https://github.com/django/django/blob/stable/1.4.x/docs/ref/templates/builtins.txt#L1096 > > > You'll see that the source for the documentation in 1.4 still has the > future-compatibility warning, and the 'old' syntax. > > This means the problem is with the Djangoproject website; for some > reason, it's showing the trunk documentation for 1.4, rather than the > docs from the actual 1.4 branch. > > This is probably an artefact of our recent move to GitHub; it's taking > a while to get all our ducks back in a row when it comes to things > like the docs that are auto generated out of source. > > I've logged a ticket to track the problem: > > https://code.djangoproject.com/ticket/18293 > > Yours, > Russ Magee %-) > > On Thu, May 10, 2012 at 8:09 AM, Greg Nicholas <greg.nicho...@gmail.com> > wrote: > > Correct me if I'm wrong, but I think 1.4's documentation has jumped the > gun > > in describing the url template tag's syntax. > > > > According to 1.4's documentation: > > > >>> {% url 'path.to.some_view' v1 v2 %} > >> > >> The first argument is a path to a view function in the > >> format package.package.module.function. It can be a quoted literal or > any > >> other context variable. > > > > > > Based on some simple tests I've run, it cannot be a quoted literal. > i.e. {% > > url myapp.views.home %} works, while {% url 'myapp.views.home' %} fails. > > > > This makes complete sense after taking a look at the docs for 1.3. It > > contains a "Forwards compatibility" section that says this quoted view > > behavior will be the standard in 1.5, and until then {% load url from > future > > %} is necessary to enable it, but the 1.4 docs describe the situation as > if > > it is already the standard. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Django users" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/django-users/-/mRBNdd771u8J. > > To post to this group, send email to django-users@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/ZmltQiOtlloJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
