Re: Is there a bug in folksonomy?

On Wed, 29 Aug 2007, Will Guaraldi wrote:

> I looked at the author's web-site and it looks like 1.4 is the last
> release he did.
>
>   http://www.timfanelli.com/projects/folksonomy_py.txt

Will and other maintainers,

Is it possible to have some explicit mechanism for detecting which 
pyblosxom API version the programmer was using?  That way, when people 
stumble across old plugins, they can see clearly that it's too stale to 
use.

I would suggest passing a mandatory keyword argument for all the callbacks 
that goes something like api_version='1.3' - if this argument is missing, 
pyblosxom shows an error page informing the user that a plugin is stale 
and the path to it.  Starting doing it with the 2.0 series would be okay. 
Even better than a generic error message would be a note saying, "This 
callback uses version 1.3 of the cb_filelist API.  That is unchanged for 
version 2.0, so try just increasing the version number", or "This callback 
uses versoin 1.3 of the cb_filestat API.  That has changed since then; see 
http://pyblosxom.sourceforge.net/something for the current docs."

This problem of old plugins was a huge problem for me as well as others 
I've helped set up pyblosxom.

-- Asheesh.

--
/earth is 98% full ... please delete anyone you can.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/