On 12/6/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > but I think it is not very good to do so, model.py depend on the > cherrypy runtime. > the program is hard to test and run without cherrypy. > so the best way is that model.py is separated from cherrypy's > config.Do you think so?
Technically, you don't *have* to use CherryPy's config module in this instance. You can instantiate your own AutoConnectHub with a URI for the database connection you want. The config mechanism for all of TurboGears is CherryPy's. I don't see a need to grow our own independent config system or to have one config for the model and other config files for other things. Is there some other separation you'd envision? I also don't think that using CP's config system in any way breaks the MVC separation. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
