Re: Re: problems with trackback

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.

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?

	-Eric

--
"Education is what remains after one has forgotten everything he learned in school."
	- Albert Einstein

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCWAp1ZWL8hfFdQekRAtvoAJ9CJ7/vUKZ+daL8T01/2JP5ecwqXgCdFjGu
GX/ouHVXKj3pEaTG7C7ezG0=
=/BjM
-----END PGP SIGNATURE-----