Re: Manually parsing a URL and returning the view name and args

That's a good point, I'll solve the problem by setting up redirects. Still it's nice to know about the resolve function. Regards, Andrew Ingram 2009/2/27 Ned Batchelder : > > I'm curious why you think view names and arguments will remain unchanged > in the future while URLs will not?  I understa

Re: Manually parsing a URL and returning the view name and args

I'm curious why you think view names and arguments will remain unchanged in the future while URLs will not? I understand you can take on the effort needed to guarantee that old view names will still work, but why not take that on for the URLs? Don't you want old bookmarks and search results

Re: Manually parsing a URL and returning the view name and args

Of course within `reverse` function there is `resolve` function that parses path and return view function, positional arguments, and named arguments. On Fri, Feb 27, 2009 at 2:33 PM, Andrew Ingram wrote: > > Hi All, > > I'm trying to to build a model which can store a link to any page on > the s

Manually parsing a URL and returning the view name and args

Hi All, I'm trying to to build a model which can store a link to any page on the site. Ordinarily I'd just use a URLField, but I want to future- proof it. Instead I'd like to store the view name (including modules) and the parameter dict. Then I'd like to be able to retrieve these later and use t