Re: Re: problems with trackback

On Apr 9, 2005, at 10:01 AM, Eric Gaumer wrote:

> Ted Leung wrote:
>> Hi Eric,
>>
>> Just so you know, I've committed a new version of trackback.py with 
>> some
>> additional changes related to the trackback spec -- Uche Ogbuchi had
>> already made them, so I've folded them in.
>>
>> I'm at a loss for why Joseph is having so much trouble -- I'd really
>> like to get to the bottom of it so that we could put some better
>> diagnostic code in the plugin so that people don't have to suffer.
>>
>> Ted
>>
>
> Okay. I actually got a pingback from Uche on this. I'll check out the
> latest version and verify it's working here.
>
> There seems to be code scattered about. Joseph I would archive what
> you have and check out a clean copy from CVS.
>
> It would probably be helpful to toggle a DEBUG directive so that people
> could enable it and be able to provide the output. What I always seem
> to end up doing is littering these plugins with print statements so 
> that
> I can see what the heck is going on and it usually points me to the
> problem. Some of the exception handlers only provide basic output; 
> hardly
> enough to get a feel for what happened. Seems half the time it's better
> to not even catch the exception so I get some call stack dump from the
> interpreter instead.

Part of the reason that there isn't a lot of debug output is that I 
debug
by running Wing's debugger against Pyblosxom to diagnose problems.  But 
I
think that a debug directive controlling log stuff is probably the right
way to go.  Steve Armstrong is overhauling the logging system, so once 
that
settles down, that would be the most appropriate way to do it.

>
> I just riddled the autoping.py script with verbose output to get it 
> working
> last night. Most of the problems I've been finding seem to be API 
> issues as
> opposed to actual logic bugs. Has the API been changing that much?

There haven't been frequent API changes, but the switch to 
request/response
objects hasn't quite made it to all the plugins (like autoping).  We 
rely on
each plugin author to update their plugins, and people are running on 
different
versions of pyblosxom.  I think that we're going to do a little better 
on keeping
the plugins aligned with the pyblosxom version.

----
Ted Leung                          Blog: <http://www.sauria.com/blog>
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click