On Wed, Jun 22, 2011 at 2:48 PM, Mark Ramm <[email protected]>wrote:
> I think it's the only way for us to control our own destiny for the > future, so I'm +1 on it. And I agree that what we ultimately want > is for tg.i18n and tg.session and tg.config to be the way we tell > everybody to use tg -- that way we expose a consistent API and make > pylons/pyramid/paste/formencode/etc into implementation details. > > When talking with Mark about the idea of exposing everything through the tg namespace instead of the pylons one he suggested the idea of monkey patching pylons to report a deprecation warning to people accessing pylons.something instead of tg.something. I think that this might be a great idea to help people migrate their apps to the tg namespace, but as it involves quite some changes, before merging it into the development branch I think it needs a bit of review and real world tests from others. The changes are available in the nru_depr_warn branch. https://sourceforge.net/p/turbogears2/tg2/ci/7826dbfdd6147227311c4023f5361362a2915025/ Still missing monkeypatching of i18n related things and caching, most of the other things should be there. -- 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.
