On Friday 07 December 2001 11:04 am, Geoffrey Talvola wrote:
> The __init__.py was just so that the config files could be imported
> as a package. �But if there are good reasons to stick with *.config,
> then obviously you can't just import the files as a package, so the
> reason for __init__.py goes away.
The reason for .config is that install.py scans for *.config, although
obviously it could scan for *Config.py and *Configs.py as well.
But perhaps the real reason to axe __init__.py for config directories
is for simplicity. I prefer fewer conventions-to-be-remembered when
that doesn't force us to give up something important.
> >We definitely have to be able to distinguish the file as install.py
> >does things with config files (which will change in nature in the
> >future, but still be a requirement).
> >
> >
> >The plan I was changing for Configurable was simply to do an exec,
> >unless the first char was a {, in which case I would do an eval.
>
> Just make sure to chop off whitespace first. �I don't know if you
> want to scan for comments before the first { or not.
Agreed. I planned on making the assignment style the de facto style
over dictionaries, so while some extra effort is nice, we don't have to
be perfect.
-Chuck
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
