Yea, but what I missed is that update config actually does: from cherrpy import config
so when they call config.update they are updating the cherrypy configuration directly. So we never really pass a configuration to cherrypy, we just use the config out of cherrpy, which has now changed in scope. Which means that application specific config was being lost. We've got this all at least mostly straitened out in the cp3 branch now. --Mark On 2/28/07, Joost <[EMAIL PROTECTED]> wrote: > > > turbogears.config.update_config (which calls cherrypy.config.update) > is called from the startup script created by quickstarting a project. > > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
