RE: New stable release coming up.

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

> -----Original Message-----
> From: pyblosxom-users-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> [mailto:pyblosxom-users-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On 
> Behalf Of Wari Wahab
> Sent: Friday, January 31, 2003 10:10 AM
> To: will
> Cc: pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Subject: Re: [pyblosxom-users] New stable release coming up.
> 
> 
> will wrote:
> 
> >I actually like the config.py way of doing things a lot.  I 
> don't use 
> >the ini file.
> >
> I'll drop INI next release, anyone with any objections?
> 
> >You're right--I was confused.  I re-read the code and realized I was
> >remembering the self.py.update(entry) stuff in reverse.
> >
> Yeah I didn't want to bloat py. I thought, hey, it (python internals) 
> must be doing a lot of work if I keep changing dict values like that, 
> knowing how bothersome it can be keeping a dynamic data 
> structure in C.
> 
> >Though the py dict still isn't global.  Also, not to be a twit, but I
> >really hate the name "py".  It should be something like 
> config or property 
> >or anything.  The name "py" doesn't lend any insight as to 
> what it holds 
> >and it additionally has other meanings in the Python language.
> >
> Aah, I was naive see? :) py being the short form of 
> pyblosxom, and I was 
> like jealous on the fact that blosxom did not need such 
> things :) So I 
> wanted something short and sweet at the time and chose py, 
> others would 
> be too tiring to type. Anyway, I did not, for once imagine pyblosxom 
> would go this far! And it did :)
> 
> >That's true--my issues are probably less with the Wiki 
> system and more
> >with the people who are running it.
> >
> Though you have to admit that they can be a good source of 
> information :)
> 
> >I'll take a look at the documentation that's floating around 
> tonight, 
> >sign
> >up for an account, and proofread and such.
> >
> Thanks
> 
> >When're you planning to release the next version of pyblosxom?  How 
> >much
> >time do we have for things?
> >  
> >
> Hopefully, if family don't get in the way :) By Sunday, the 
> max deadline 
> for me is Tuesday night, as I'll start work on wednesday.
> 
> 
> 
> -------------------------------------------------------
> 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
>