Max Ischenko 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? > > I checked my code and detected following dependencies on CP: > > cherrypy.HTTPError (as well as NotFound and HTTPRedirect) > cherrypy.request > cherrypy.response > > Doing dir(cherrypy) added the following: > > InternalError <type 'classobj'> > InternalRedirect <type 'classobj'> > NotReady <type 'classobj'> > log <type 'function'> > root <type 'NoneType'> > server <class 'cherrypy._cpserver.Server'> > session <type 'instance'> > tree <type 'instance'> > > If you know more, let's add them. > > 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?
+1. The sooner we do this, the better. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
