current_route_url() is there because people like to generate new urls with the same matchdict as the current url or by modifying only one of the matchdict parameters a la current_route_url(id=5). It's equivalent to pylons url.current(). Its usage is, of course, documented.
http://docs.pylonsproject.org/projects/pyramid/en/1.4-branch/api/request.html?highlight=current_route_url#pyramid.request.Request.current_route_url On Fri, Dec 7, 2012 at 11:44 AM, Mike Orr <[email protected]> wrote: > > Also request.current_route_url() is way slower than just doing >> request.url if you just want the current url. >> >> > So when would you use it, or is it just there for completeness? > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" 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/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
