Re: [Pyblosxom-devel] Thoughts on pyblosxom-cmd

[will kahn-g. <wi...@bl...>]

On 04/01/2011 09:38 AM, seanh wrote:
> 1. Is there a reason why the command is pyblosxom-cmd and not just
> pyblosxom?

Yes.  It was originally pyblcmd or something short like that, but I
decided it's better to make it unambiguous.  If people use it a lot,
they can always alias it.


> 2. Can `paster serve blog.ini` be integrated into pyblosxom-cmd?
> Something like `pyblosxom-cmd serve`.
> 
> If it can't work because paster is not installed it should print out a
> helpful message saying paster is not installed, try `sudo pip install
> PasteDeploy` (or whatever is should be).
> 
> And the command would not to be run inside a pyblosxom blog dir with a
> blog.ini and config.py (or perhaps a subdirectory thereof), otherwise it
> would print out a helpful message explaining so.
> 
> Optional command-line option to specify the blog directory to use
> instead of the current working directory.

There's a commandline callback.  I'd love to implement this as a plugin
to get the details right.  If it's good, I'd be game for adding it to
the core code (not as a plugin--but actually as core code).

It might not have to use paster, either.  It might work fine with stdlib
stuff.  This might be a compelling reason to up the python version
requirement again.

/will