So, many of our tests are very tightly coupled with the CP2 way of doing things. But the actual TurboGears code is not nearly so tightly coupled, and we are now able to process requests with a quickstarted app (we get a stacktrace due to some configuration work that isn't yet done, but we can fake it.
Internal server calls need to change, and we probably need to determin the API we want to use for mounting applicaitons at other places than the root. Once we get things working in an acutal applicaton, we plan to go back and write some new tests that are less tightly coupled to CherryPy. The nicest bit so far is cherrypy.url which will let us make the turbogears url() function way less complicated. Woo--hoo for code removal!!! So far we have only one change that will impact end users so far: * simple_cookie has become cookie on both the request and response objects. If you're interested in following along, all of this work is happening in the cp3 branch. -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
