Re: New stable release coming up.

will wrote:

>I think you guys are crazy.  I've done development for a long time and it
>just seems silly to me not to have that additional buffer between your
>"production" code and your "development" code.  Though I guess these are
>just weblogs, so it probably doesn't matter so much.
>  
>
Just depends on what you're doing :) I for one would love to see what 
breaks pyblosxom, at least your data does not live in pyblosxom's CVS 
directory I guess it's OK, anyway, you can always check out the previous 
revisions.

>I use my weblog walks through the status on the projects I'm working on
>and I know people check it frequently enough that if my weblog were to
>become non-operational for a few hours, it'd be a pain.
>  
>
Yeah, when that happens, aldrenalin rises and I'm up to fix what ever I 
did :) The pyblosxom website is a good website to kill things. When it's 
dead it means I'm doing something, though I know that's bad practice, 
just the way I work.

>I'd be up for Ted's idea for using defaults and then an example-config.py.  
>Though I should note that if you add a:
>
>   sys.insert(0, "/path/to/dir/with/config/")
>
>to the top of your pyblosxom.cgi script, then you can put your config.py 
>wherever you like as well.
>  
>
Where and what could we put in as defaults? One thing about defaults is 
that when you install pyblosxom, it will still not work the first time 
as you have to at least point your datadir somewhere in the first place 
or place in a reasonable default ('../blog').