[Pyblosxom-devel] Egads! Bugs?

['Wari W. <wa...@ce...>]

BTW, I cc to pyblosxom-devel as this topic spawns of to something that
devel list might me interested in.

* Blake Winton <bl...@ph...> [030204 22:57]:
> So, have you gotten any bug reports recently?

Being a python software (unlike perl blosxom) I don't have that much
users giving me bug reports, if they have, they included a patch for it
(interesting indeed).

> Are you using any of the SourceForge features, other than the mailing
> lists?  

Tried to but with miniscule user base, I don't see sf.net to be a main
focal point of activity.

> I notice that they have a place for bug tracking and another for
> documentation.  

The documentation thingy is not as good as a wiki I guess, that's why I
have a wiki site for documentation. Anyone who feels that the docs is
lacking can always contribute if they need to.

> If anyone is submitting bugs, I'd love to help track them down and
> fix them.  (Of course, if no-one is submitting bugs, good job! ;)

Bugs, what bugs? pyblosxom is 1000% bug free :) NOT. hehe. There is one
or two lying about.

1. Entry files that starts with a digit will fail to get picked up by
   pyblosxom when using a single entry link:
   See:
   http://roughingit.subtlehints.net/pyblosxom/2003/Jan/31#1044019277
   http://roughingit.subtlehints.net/pyblosxom/development/1044019277.html

   The second url borks. This bug requires some modification (or even
   refactoring) of libs.Pyblosxom.startup() or could even be done better
   with a urlhandler() thingy, which is not available yet. Which is why
   I didn't fix this before releasing 0.6

2. Proper url handler to handle things queries like 2003/Jan/index.html
   or /development/index.html

I think the main point of this is that handling or URLs must be fixed or
pluggable so that we can do sane URL handlings or handle other stuff
like comments or searches, etc..

-- 
Regards: Wari Wahab
Senior R&D Engineer
Celestix Networks
http://www.celestix.com/