Most of the pylons things used by TurboGears are accessible from the tg.* namespace directly. I think that this is indeed good as it keep an high level of abstraction from pylons itself and gives use more freedom for future evolutions.
I was thinking to take a look around in the documentation, look of each pylons.something function used inside the doc and migrate it to tg.something. Also if in the process I discover something that isn't available inside the tg namespace I woud expose it inside tg itself. What is others opinion about this? Any one against doing this? Alessandro -- 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.
