On 4/10/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > > > As I see it, TG shifts slowly from cherrypy in anticipation of FirstClass > branch. > > We already have turbogears.redirect and turbogears.config to abstract > corresponding CP's objects. > > How about abstracting HTTP exceptions like cherrypy.NotFound and other CP > globals, like request and response?
[snip] > 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. > > What do you think? > Should I submit a ticket? 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. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
