Re: Small paster related bug and its fix.

Will,

You did reply, and it was similar. Thanks for both responses :)

Regards,
Erich

On Sun, May 3, 2009 at 7:37 PM, will <[email protected]> wrote:

> I can't remember if I replied to this or not.  If I did, hopefully I said
> something similar.
>
> "old-trunk" vs. "new-trunk" is only a useful distinction in regards to
> current development.  A month or two (or three) ago, I switched gears in
> regards to the next version.  After the nedt version is released, the whole
> "old-trunk" vs. "new-trunk" will be moot.
>
> My vote is to keep running pyblosxom 1.4.  I have some minor things to do
> for 1.5, but I still need to do some testing and see how the changes I've
> made affect plugins.  Getting there, but haven't gotten there yet.
>
> Having said that, if enterprising souls want to help me test out and
> identify issues with what's in trunk right now, that'd be really awesome.
>  Patches are hugely helpful.
>
> /will
>
>
> 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
>>
>

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel