Rene Dudfield wrote: > On 8/24/05, Phillip J. Eby <[EMAIL PROTECTED]> wrote: > >>I'm not sure what you mean by SQL DB, but if you mean putting the >>configuration in a database, I don't see why that would be useful or >>good. Similarly, I don't know what you mean by "file system". >> > > > By sql db I meant storing configuration in a database. Which has many > advantages including scaling, searching, ACID, permissions etc etc.
Do you mean like putting the configuration files in a database? That shouldn't be a problem if there's a consistent way to access files (pkg_resources?) that handles (or has an interface for) virtual file systems. If it doesn't go in initially, I expect it would be a simple refactoring otherwise. If you don't intend to use text configuration files, then you'd have to code your own logic to put the pieces together. This is perfectly fine to do, and quite reasonable as well. If, for instance, you were doing some system where new applications were deployed automatically based on a very constrained configuration, you can easily do that programmatically in Python without involving any configuration files. -- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org _______________________________________________ Web-SIG mailing list [email protected] Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
