Re: New stable release coming up.

FWIW, I agree with Ted.

I have no issue with the ini file going away, I don't think it's any 
harder to edit a python file then an ini file.  However It would be nice 
if the all the configuration stuff was only in one file.  That way I can 
do a CVS check out (or even untar a release) over the top of my running 
directory and not worry about my configs getting overwritten.

So, maybe something like blosxom.cgi holds the default config values 
(and they can be edited there) but if wanted/needed you can over ride 
them on a case by case basis in config.py (and config.py shouldn't exist 
in or a distro, though you could have a config-example.py or something 
if you were so inclined).

This is also similar to the way Moin works.

Adam.

will wrote:
> Um...  I don't know if I would run my blog off of my CVS directory.  I 
> would think you'd want a step between you and CVS in case someone drops 
> something in that causes things to break.
> 
> Then you can have changes in your blog system and not have to worry about 
> accidentally commiting those to the repository.
> 
> So, I guess this is a word of caution against the setup I'm inferring that 
> you have.
> 
> /will
> 
> 
> On Fri, 31 Jan 2003, Theodore W. Leung wrote:
> 
>>Hi all,
>>
>>I'm back from travelling (at least for this week) and trying to catchup.
>>
>>I like the INI file because it makes it easier for me to customize settings
>>and not have a config.py that is drastically different from what's in CVS.
>>But if you drop it I'll cope.
>>
>>Ted
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> pyblosxom-users mailing list
> pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users