Re: Small paster related bug and its fix.

It's a pretty short story.  I released PyBlosxom 1.4.3 on January 10th, 
2008 and started working on PyBlosxom 2.0.  I got caught up in other 
things and ended up sitting on it for a year.  Feature creep was 
happening in spades, I was having a tough time remembering where I was 
with development, and I didn't have enough momentum to get through it. 
So a little over a month ago I declared "bankruptcy" on PyBlosxom 2.0 
and started over with a smaller more defined milestone of PyBlosxom 1.5.

Instead of ditching all the work that was done for 2.0 for good, I put 
it in the experimental directory and rebased trunk from the 1.4.3 tag. 
Then I pulled a bunch of stuff over from the "old trunk" into the new 
trunk.  That's where we find ourselves today.



Erich Heine wrote:
> Cool. Glad its in there :). What is the old-trunk/new-trunk distinction? 
> I'm totally new to pyblosxom so if it's on the website somewhere just 
> point me at it and I'll go read.
> 
> To clarify a bit: I'm not yet running trunk for my blog. I decided to 
> run 1.4 for a while because it's easier to see if I'm making a n00b 
> mistake w/ config, or if there is a trunk bug. I just noticed that the 
> configini thing was broken in trunk as well as 1.4. I do however plan on 
> switching to trunk at some point, so I will let you know if anything 
> comes up.
> 
> Regards,
> Erich
> 
> On Sun, Apr 5, 2009 at 8:38 AM, will <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>     Whoops!  Looks like you found one of the things that was fixed in
>     the old trunk that hadn't gotten fixed in the new trunk yet.
> 
>     Thanks for the patch and the heads-up!  I committed it in r1307.
> 
>     I'm psyched you're running trunk!  I haven't started using it on my
>     blog yet, so I'm not wholly sure how stable it is.  If you bump into
>     anything else, let me know.
> 
>     /will
> 
> 
> 
>     Erich Heine wrote:
> 
>         Hi all,
> 
>         I literally just signed up for this list, and I hope I'm not
>         violating any protocols here...
> 
>         I had a small problem when trying to get pyblosxom running with
>         paster serve. I would get a KeyError for config options set only
>         in the blog.ini file (my config.py was only: py = {} ).  Patch
>         to fix this (against trunk is included below).
> 
>         A quick description is that the app_factory was doing a bunch of
>         config setup, and then passing the resulting dict to
>         PyBlosxomWSGIApp as a positional parameter. The problem is that
>         class wants env as the first positional parameter, not config
>         data (that keyword is third...).
> 
>         Anyway, hope this helps.
> 
>         Regards,
>         Erich

------------------------------------------------------------------------------