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 argument string and parameters that turn into querrystring params the basic tg1 url functionality is preserved. There are a couple things that won't work quite as they did in tg1. Well, the only one that I can think of is that url will no longer take a list of items and concatenate it with url separators. But I think this loss is far outweiged by the fact that url will handle routes effectively, and will behave in the same way across TG and Pylons, and the same as routes url_for function. For redirect, I would like to basically turn redirect into a very thin wrapper around url. Basically it would take it's arguments pass them to url, and then redirect the user to that url. If we're going to make this change, and I think we should, we need to make it now. Any thoughts? -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
