Re: is anyone using return_folders in tools.Walk()?

On 7/6/07, Ryan Barrett <pyblosxom-6sb6M7qyT/[email protected]> wrote:
>
> agreed. i'll start on this. i'll change the pyblosxom and contrib calls to use
> os.walk, and we can encourage plugin developers to switch to it. for the time
> being, i'll deprecate tools.Walk and leave a compatibility shim in.
>
> btw, plugin developers, consider yourselves encouraged. :P
>
> -Ryan

Oh whoops--I meant that we should refactor tools.Walk to use os.walk.
There are some filtering things that tools.Walk does that we want to
maintain.  I'm also interested in splitting tools.Walk into a
tools.get_entries and a tools.get_categories (or something along those
lines--something that's more semantically oriented and closer to the
API we want to provide plugin writers).

I think I'd want to work this out in design before committing to
anything.  If only to get a better handle on what we can do here and
what requirements there are.  For example, do we want to add hooks
allowing plugins to provide their own get_entries and get_categories
methods?  Would this help plugins that support tagging?  Should we
attempt to fix PyBlosxom such that someone could build a plugin that
stores and retrieves entries from SVN or a database instead of the
filesystem?  ...

/will

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/