Re: Re: problems with trackback
Eric Gaumer <gaumerel-rO34MGDSYikxZu/[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Message-ID | <[email protected]> |
Ted Leung wrote: >> >> 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. > Alright I'll be looking for that new logging system. Providing a very verbose mode will shake out many of the problems that people seem to be having lately. I would be more than happy to go through the code and supply useful output for debug purposes. It'll give me a chance to familiarize myself with the API. >> >> 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. > Why are plugins developed separately? I can see the need for non-core plugins but can't some of the basic ones be maintained and distributed with the core pyblosxom code? Things like xmlrpc, xmlrpc_metaweblog, comments, and autoping seem to me like core functionalities of a blogging system. -Eric -- "Education is what remains after one has forgotten everything he learned in school." - Albert Einstein
signature.asc
(application/pgp-signature, 256 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCWbQcZWL8hfFdQekRAqMNAKC8J3rPFtES0WqITLPUdtzRwrYH0wCfRi8L PzZLQRlC8WjDrp0I7RwZMRo= =cm1Q -----END PGP SIGNATURE-----