Re: spambayes plugin, and other plugins

will <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <[email protected]>
Ryan Barrett wrote:
> On Thu, 6 Dec 2007, will wrote:
> 
>> What other higher priority stuff is there?
> 
> all of the 2.0 work? granted, it's a little more forward looking, but 
> i'd rather see progress on that than yet another (nontrivial) spam plugin.

Most of the 2.0 stuff isn't very self-contained task-wise.  A large 
portion of it involves figuring out what 1.4 did, figuring out what 
PyBlosxom 2.0 should be doing and then making the necessary adjustments. 
  At least, that's how I've been working through 2.0 stuff.

The first round of tasks involved updating the registry.  We had four 
tasks in the first round for going through plugins in the registry and 
figuring out what their status was.  Two of those tasks have been 
completed and unearthed some problems with plugins.  The other two 
haven't been completed yet.

I've got four more tasks for the next round for things that need to be 
done in the wake of current PyBlosxom 2.0 changes.  One for converting 
the rst entryparser into a formatter, one for building the entryshelve 
plugin, one for building the entrypickle plugin, and one for writing a 
report on PyBlosxom's memory footprint when running as a CGI script, as 
a long-running process under Paste, and in static rendering mode.


> as a concrete alternative, i'd love to see more unit test coverage. the 
> lack of unit tests is one of the main reasons i don't work on pyblosxom 
> more. (ok, that and a lack of free time. :P)

I've been working on adding unit tests as I make changes for PyBlosxom 
2.0, but it's been slow going.  The biggest problem I'm running into is 
that very little of PyBlosxom is well-specified, so writing unit tests 
often requires figuring out how xyz is supposed to behave and in weird 
corner cases trying to figure out what's going on and what it should be 
doing.

PyBlosxom 1.4.3 will have 33 tests.  PyBlosxom 2.0 currently has 50 
tests with a coverage score of 36%--but I think that's not right and too 
high.

Adding some unit test related tasks is a good idea.  I'll do that in the 
next round.  Some of the other projects have had tasks along the lines 
of "improve test coverage to xyz percent."  That'd help a lot.

/will

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.