> > What I propose is to make these names available through the TurboGears > > namespace so > that we'll be future-safe. I know about YAGNI, but the transition already > started so we > shouldn't stop halfway, IMO. > > I'd rather take this action during the First Class work itself. > Because, for some of the things, it's unclear right now what exactly > we'd suggest people to use instead. (Sessions? cherrypy.root?) The > mechanism may be completely different. Besides, RhubarbTart offers > some cherrypy compatibility. > > In First Class itself, I'd like to take over the cherrypy names for > backwards compatibility and put up informative DeprecationWarnings as > needed.
Point taken. It's unclear right now what exactly we'd suggest people to use instead of sessions, root or filters. But what about "simpler"/more common things like request, response and error classes (HTTPError and NotFound)? I'd say promoting them is OK. After all, we do promote turbogears.config and turbogears.redirect. So these will become: turbogears.request turbogears.response turbogears.http_error turbogears.not_found --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
