Here's a shitty alternative that highlights the best points of your
class-based suggestion:
##
def S(**kw): return kw
AppServer = S(
Applictions = S(
MyApp = S(
Dirs = S(Products = '/home/tavis/Webware/Products'
Services = '/home/tavis/Webware/Ser
On Monday 10 December 2001 13:42, Geoffrey Talvola wrote:
> In your own example above, importing the config file actually
> _creates_ two instance of application classes. This could have
> side effects that you don't expect to get just by loading a config
> file. It might cause lines to be writt
On Monday 10 December 2001 13:42, Geoffrey Talvola wrote:
> Why not just put the "magic" part into a separate source file? I
> don't see how putting this kind of stuff directly into the config
> file gains any real power.
The end result would be the same either way, but I prefer doing it
direct
At 02:39 PM 12/10/01 -0800, Tavis Rudd wrote:
>On Monday 10 December 2001 13:11, Geoffrey Talvola wrote:
> > At 01:59 PM 12/10/01 -0800, Tavis Rudd wrote:
> > >Geoff,
> > >going back to your class-based config syntax...
> > >
> > >The reason we'd need to subclass SettingsContainer is that it is
>
On Monday 10 December 2001 13:11, Geoffrey Talvola wrote:
> At 01:59 PM 12/10/01 -0800, Tavis Rudd wrote:
> >Geoff,
> >going back to your class-based config syntax...
> >
> >The reason we'd need to subclass SettingsContainer is that it is
> >possible to have settings that are in fact classes and d
At 01:59 PM 12/10/01 -0800, Tavis Rudd wrote:
>Geoff,
>going back to your class-based config syntax...
>
>The reason we'd need to subclass SettingsContainer is that it is
>possible to have settings that are in fact classes and don't begin
>with an underscore:
>
>##
>from SettingsManager import Set
