Re: computing url for view registered by name

2011-03-05 Thread Michael Merickel
By leaving out the context you are effectively registering those views to *any* context, which is almost always undesirable. Regardless, my previous reply remains correct, if you want the path hanging off of /, simply use resource_url(request.root, request) and resource_url(request.root, request,

Re: computing url for view registered by name

2011-03-04 Thread Chris Withers
On 01/03/2011 16:59, Jean-Philippe wrote: First off, I believe your views need to be named for this to work. But views don't need to have names ;-) That being said, the following would work from within a view callable: url = request.route_path('history') ...not if I'm not using a

Re: computing url for view registered by name

2011-03-01 Thread Michael Merickel
I noticed in your example you aren't specifying a context= or for_= in the view_config, implying you maybe intended to use route_name instead of name with url dispatch. If you are using traversal your application basically assumes a resource tree, and so to get the url you provide a resource