Mark Ramm schrieb:
Ok, this is done.
The url and redirect functins no longer take lists of path elements,
and no longer take dictionaries of parameters -- so you need to append
your path elements manually now, and you need to do *dict to turn your
dictionary into keyword arguments if you
+1
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Trunk group.
To post to this group, send email to turbogears-trunk@googlegroups.com
To unsubscribe from this group, send email to
On Mon, Dec 15, 2008 at 11:11 AM, Mark Ramm mark.mchristen...@gmail.com wrote:
I propose that we switch to using the pylons.url function which is
routes aware in tg2.
--8--snip--8--
Any thoughts?
+1
--
Lee McFadden
blog: http://www.splee.co.uk
rejaw: http://rejaw.com/splee
twitter:
On Mon, Dec 15, 2008 at 2:11 PM, Mark Ramm mark.mchristen...@gmail.comwrote:
I propose that we switch to using the pylons.url function which is
routes aware in tg2.
[...]
If we're going to make this change, and I think we should, we need to
make it now.
Any thoughts?
This sounds like a
Ok, this is done.
The url and redirect functins no longer take lists of path elements,
and no longer take dictionaries of parameters -- so you need to append
your path elements manually now, and you need to do *dict to turn your
dictionary into keyword arguments if you want those passed as
On Mon, Dec 15, 2008 at 1:11 PM, Mark Ramm mark.mchristen...@gmail.com wrote:
I propose that we switch to using the pylons.url function which is
routes aware in tg2.
This means that those using routes can use tg.url the same way that
they expect, and because pylons.url accepts a first
