pyblosxom-users — Mailing list for pyblosxom users and hackers.

Re: [pyblosxom-users] hardcoding mtimes for stories in their metadata section

[Tim G. <tg...@pr...>]

On Nov 01, 2010 at 03:11 PM +0100, Dieter Plaetinck wrote:
> Thanks, this is actually another plugin then the one I was looking for.

Yeah I wrote this from scratch the other month.

> Notice that both the description for cb_prepare as well as the big
> comment block on top of your file imply that they reset/ignore mtime
> first, and then update using the info from the metadata.  This is not
> correct, from looking at the code it seems that the pubdate can
> override the mtime, but the mtime is not discarded if there is no
> pubdate.

That is correct.  If there is not pubdate/pubtime, then the file's mtime is 
used.  If I recall correctly, the if those variables aren't set in the post 
file, $(pubtime), $(pubdate), $(displaytime), and $(displaydate) are all 
populated by the file's mtime, so you can use the same set of templates and 
mix files with hardcoded dates and files with mtime encoded dates.

I think cb_prepare's comment reflects that fact that during the cb_sortlist 
loop (which occurs before), a file's pubtime is set according to the mtime 
if #pubtime/#pubdate doesn't exist.  So once you get to cb_prepare, we DO 
ignore file's actual mtime - it's already been taking into account.

Re: [pyblosxom-users] hardcoding mtimes for stories in their metadata section

[Dieter P. <di...@pl...>]

On Mon, 1 Nov 2010 09:56:02 -0400
Tim Gray <tg...@pr...> wrote:

> On Nov 01, 2010 at 02:23 PM +0100, Dieter Plaetinck wrote:
> > Aha, i thought I found such a thing at some point, but couldn't
> > find it back.
> > Where is this plugin?  I'll try it out, not too worried about the
> > performance hit right now, but if it becomes noticeable I can
> > always add caching.
> 
> Yeah it's on my huge list of things to do: add caching.  I'm using
> this on a site with about 450 posts right now though and don't notice
> too big of a performance hit.
> 
> Here's a link to it:
> <http://dl.dropbox.com/u/100367/pymetatime.py>

Thanks, this is actually another plugin then the one I was looking for.
I remember seeing a plugin like this somewhere but it had a comment
somewhere noting that "this is not very efficient, we need to read the
file in this step and pyblosxom will read the file itself as well, but
that's how it works now, so..." or something like that

Anyway I'll try out your plugin.
Notice that both the description for cb_prepare as well as the big
comment block on top of your file imply that they reset/ignore mtime
first, and then update using the info from the metadata.  This is not
correct, from looking at the code it seems that the pubdate can
override the mtime, but the mtime is not discarded if there is no
pubdate.

Dieter

Re: [pyblosxom-users] hardcoding mtimes for stories in their metadata section

[Tim G. <tg...@pr...>]

On Nov 01, 2010 at 02:23 PM +0100, Dieter Plaetinck wrote:
> Aha, i thought I found such a thing at some point, but couldn't find it
> back.
> Where is this plugin?  I'll try it out, not too worried about the
> performance hit right now, but if it becomes noticeable I can always add
> caching.

Yeah it's on my huge list of things to do: add caching.  I'm using this on a 
site with about 450 posts right now though and don't notice too big of a 
performance hit.

Here's a link to it:
<http://dl.dropbox.com/u/100367/pymetatime.py>

Re: [pyblosxom-users] hardcoding mtimes for stories in their metadata section

[Dieter P. <di...@pl...>]

On Mon, 1 Nov 2010 08:55:41 -0400
Tim Gray <tg...@pr...> wrote:

> On Nov 01, 2010 at 12:13 PM +0100, Dieter Plaetinck wrote:
> > Hi all,
> > is it possible to hardcode the mtime for a story in its metadata
> > section?
> 
> I wrote a nasty plugin that does this.  At this point, there is no
> caching and the code isn't exactly clean, but it does work.

Aha, i thought I found such a thing at some point, but couldn't find it
back.
Where is this plugin?  I'll try it out, not too worried about the
performance hit right now, but if it becomes noticeable I can always add
caching.

Dieter

Re: [pyblosxom-users] showing source code in blog posts

[Dieter P. <di...@pl...>]

Well, like I said, the pages are rendered exactly like they were before
and my lighttpd logs contain no errors (and the pyblosxom logging
doesn't work for me, but that's another story)

There definitely are \n in the text.
In fact, I now tried this:

in plugins/comments.py:
def cb_preformat(args):
    return ''.join(args['story']) + '<h1>comments</h1>'

in plugins/pygments.py:
def cb_preformat(args):
    return ''.join(args['story']) + '<h1>PYGMENTS</h1>'


Then my rendered stories contain '<h1>comments</h1>', but not
'<h1>PYGMENTS</h1>'
I also tried putting the pygments plugin first in py["load_plugins"] in
the config.py, but no change.

here's the entire pygments.py source code
http://sprunge.us/TGST
I checked permissions/ownership, it's correct (and the same as the
other plugins)
This is my entire config:
http://sprunge.us/OfGb

Dieter



On Mon, 01 Nov 2010 08:46:00 -0400
will kahn-greene <wi...@bl...> wrote:

> When you say "I can't get it to work", what does that entail?  What's
> failing?  Does it do something, but not the right thing?  Are there \n
> in the text?  Is there an error?...
> 
> 
> On 11/01/2010 05:50 AM, Dieter Plaetinck wrote:
> > 
> > Thanks, that seems like a good idea.
> > I've been looking at the markdown and linebreak parser plugins to
> > see how to do it, but I can't get it to work.
> > Just to get the first step working (modifying the page content), I
> > use this code (comments stripped for clarity):
> > 
> > 
> > __author__ = 'Dieter Plaetinck <di...@pl...>'
> > __version__ = "0.1"
> > PREFORMATTER_ID = 'pygments'
> > 
> > import re
> > def cb_preformat(args):
> >     if args['parser'] == PREFORMATTER_ID:
> >         return parse(''.join(args['story']))
> > 
> > def parse(text):
> >     text = re.sub('\n','<h1>somethinghappens</h1>',text)
> >     return text
> > 
> > 
> > and my config:
> > $ grep pygment /srv/http/dieterblog/config.py
> > py["load_plugins"] = ["comments", "tags", 'pygments']
> > py['parser'] = 'pygments'
> > the code is in this file: /srv/http/dieterblog/plugins/pygments.py
> > 
> > Normally I should see "<h1>somethinghappens</h1>" all over the
> > place, right?  But my pages are the way they were before, as if
> > it's still using the plain parser.  When I use the debug renderer
> > it confirms that Request.get_configuration() dict contains parser
> > -> pygments
> > 
> > No errors in my lighttpd error log either.
> > 
> > Dieter
> > 
> > ------------------------------------------------------------------------------
> > Nokia and AT&T present the 2010 Calling All Innovators-North
> > America contest Create new apps & games for the Nokia N8 for
> > consumers in  U.S. and Canada $10 million total in prizes - $4M
> > cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt
> > SDK, Web Runtime, or Java and Publish to Ovi Store
> > http://p.sf.net/sfu/nokia-dev2dev
> > _______________________________________________ pyblosxom-users
> > mailing list pyb...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
> > 

Re: [pyblosxom-users] hardcoding mtimes for stories in their metadata section

[Tim G. <tg...@pr...>]

On Nov 01, 2010 at 12:13 PM +0100, Dieter Plaetinck wrote:
> Hi all,
> is it possible to hardcode the mtime for a story in its metadata
> section?

I wrote a nasty plugin that does this.  At this point, there is no caching 
and the code isn't exactly clean, but it does work.

Re: [pyblosxom-users] showing source code in blog posts

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

When you say "I can't get it to work", what does that entail?  What's
failing?  Does it do something, but not the right thing?  Are there \n
in the text?  Is there an error?...


On 11/01/2010 05:50 AM, Dieter Plaetinck wrote:
> 
> Thanks, that seems like a good idea.
> I've been looking at the markdown and linebreak parser plugins to see
> how to do it, but I can't get it to work.
> Just to get the first step working (modifying the page content), I use
> this code (comments stripped for clarity):
> 
> 
> __author__ = 'Dieter Plaetinck <di...@pl...>'
> __version__ = "0.1"
> PREFORMATTER_ID = 'pygments'
> 
> import re
> def cb_preformat(args):
>     if args['parser'] == PREFORMATTER_ID:
>         return parse(''.join(args['story']))
> 
> def parse(text):
>     text = re.sub('\n','<h1>somethinghappens</h1>',text)
>     return text
> 
> 
> and my config:
> $ grep pygment /srv/http/dieterblog/config.py
> py["load_plugins"] = ["comments", "tags", 'pygments']
> py['parser'] = 'pygments'
> the code is in this file: /srv/http/dieterblog/plugins/pygments.py
> 
> Normally I should see "<h1>somethinghappens</h1>" all over the place,
> right?  But my pages are the way they were before, as if it's still
> using the plain parser.  When I use the debug renderer it confirms that
> Request.get_configuration() dict contains parser -> pygments
> 
> No errors in my lighttpd error log either.
> 
> Dieter
> 
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
> 

Re: [pyblosxom-users] hardcoding mtimes for stories in their metadata section

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

w3cdate adds a variable to the story plugin.  I don't know offhand if
that's needed anymore--I think PyBlosxom adds it on its own now.  That's
definitely not what you're looking for.

pyfilenamemtime is probably the closest.  The advantage of putting the
mtime in the filename is that it can be picked up from os.listdir rather
than forcing PyBlosxom to open, read, and parse every entry on your blog
for the metadata.  If you did something like pyfilenamemtime but instead
store the mtime in the metadata, I encourage you to add some caching so
that PyBlosxom doesn't have to open, read, and parse every entry in your
blog to assemble all the files and mtimes to sort and display in a blog
timeline.  I think something along the lines of what I do in tags would
work.

/will


On 11/01/2010 07:13 AM, Dieter Plaetinck wrote:
> Hi all,
> is it possible to hardcode the mtime for a story in its metadata
> section?
> I.e. something like:
> 
> $ cat entries/post.txt
> Title of the post
> # mtime 2010-10-30 12:00:00
> hello, (..)
> 
> 
> I think these plugins are not appropriate for me: 
> - "wrapper scripts" that change the mtime back to what
> it was before editing (not very robust if you work on multiple systems)
> - plugins who cache the mtime (I want to dictate what the mtime must
> be, which is more robust)
> - pyfilenamemtime, the plugin who stores the mtime as part of the
>   filename is pretty close, but makes filenames messy, and I don't want
>   to rename the file in my vcs just to change the date
> - the w3cdate plugin is also interesting, it seems to be close to what I
>   want, but it creates a new variable instead of updating the mtime.
>   What's the point of that?
> 
> I think I will write a fork of the pyfilenamemtime plugin which uses
> the metadata section instead of the filename.
> Or am I missing something?
> 
> Dieter
> 
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
> 

[pyblosxom-users] hardcoding mtimes for stories in their metadata section

[Dieter P. <di...@pl...>]

Hi all,
is it possible to hardcode the mtime for a story in its metadata
section?
I.e. something like:

$ cat entries/post.txt
Title of the post
# mtime 2010-10-30 12:00:00
hello, (..)


I think these plugins are not appropriate for me: 
- "wrapper scripts" that change the mtime back to what
it was before editing (not very robust if you work on multiple systems)
- plugins who cache the mtime (I want to dictate what the mtime must
be, which is more robust)
- pyfilenamemtime, the plugin who stores the mtime as part of the
  filename is pretty close, but makes filenames messy, and I don't want
  to rename the file in my vcs just to change the date
- the w3cdate plugin is also interesting, it seems to be close to what I
  want, but it creates a new variable instead of updating the mtime.
  What's the point of that?

I think I will write a fork of the pyfilenamemtime plugin which uses
the metadata section instead of the filename.
Or am I missing something?

Dieter

Re: [pyblosxom-users] showing source code in blog posts

[Dieter P. <di...@pl...>]

On Mon, 1 Nov 2010 10:10:51 +1100
Pete Goldsmith <bon...@gm...> wrote:

> What about writing a plugin that parses your <code> blocks and runs
> them through something like http://pygments.org/
> 
> ?

Thanks, that seems like a good idea.
I've been looking at the markdown and linebreak parser plugins to see
how to do it, but I can't get it to work.
Just to get the first step working (modifying the page content), I use
this code (comments stripped for clarity):


__author__ = 'Dieter Plaetinck <di...@pl...>'
__version__ = "0.1"
PREFORMATTER_ID = 'pygments'

import re
def cb_preformat(args):
    if args['parser'] == PREFORMATTER_ID:
        return parse(''.join(args['story']))

def parse(text):
    text = re.sub('\n','<h1>somethinghappens</h1>',text)
    return text


and my config:
$ grep pygment /srv/http/dieterblog/config.py
py["load_plugins"] = ["comments", "tags", 'pygments']
py['parser'] = 'pygments'
the code is in this file: /srv/http/dieterblog/plugins/pygments.py

Normally I should see "<h1>somethinghappens</h1>" all over the place,
right?  But my pages are the way they were before, as if it's still
using the plain parser.  When I use the debug renderer it confirms that
Request.get_configuration() dict contains parser -> pygments

No errors in my lighttpd error log either.

Dieter

Re: [pyblosxom-users] showing source code in blog posts

[Pete G. <bon...@gm...>]

What about writing a plugin that parses your <code> blocks and runs them
through something like http://pygments.org/

?

On Mon, Nov 1, 2010 at 09:08, Dieter Plaetinck <di...@pl...> wrote:

> Hi all,
> is anyone showing source in pyblosxom blog posts?
> <snip>
>

[pyblosxom-users] showing source code in blog posts

[Dieter P. <di...@pl...>]

Hi all,
is anyone showing source in pyblosxom blog posts?
I'm in the process of migrating from a drupal blog to pyblosxom (*)
But one stumbling block is currently showing source code.
On Drupal the common solution is using geshi, a php-based syntax
hilighter.
an example to see how it looks like:
http://dieter.plaetinck.be/tweaking_lighttpd_stat_performance_with_fcgi-stat-accel
The code is something like:
<code lang="c">
some_C_code_here
<h1>some html</h1>
some_more_C
</code>

With pyblosxom, the <code> tag is just ignored and everything in
between is parsed as if it's normal html.
There are also syntax schemes for other languages like php, but this is
not even my main concern, if I could just make pyblosxom escape the
stuff between <code> tags and maybe put a <pre>..</pre> around it, it
would already be a nice step forward.

How can I solve this?

Thanks,
Dieter


(*) I'm writing a tool which is pretty useful for this:
http://github.com/Dieterbe/drupal-to-pyblosxom

Re: [pyblosxom-users] Tag Fail

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

That's a bug that was fixed, but I can't remember if the fix in the
1.5rc2 tarball or not.  It's definitely fixed in git.

/will


On 10/13/2010 11:28 AM, andrew fitting wrote:
> 
> Will,
> 
> Thanks for your continued support.  I did try most of what's there.  I'm attaching the results of pyblosxom.cgi to the end of this message.  The apache error_log shows the same trace that the previous pyblosxom-cmd does: a KeyError on form inside the cb_head function of tags.  In the debugger, form is a FieldStorage object with no keys.
> 
> Uncaught exception. Entering post mortem debugging
> Running 'cont' or 'step' will restart the program
>> /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/cgi.py(558)__getitem__()
> -> raise KeyError, key
> (Pdb) u
>> /Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py(408)cb_head()
> -> flavour = config.get("default_flavour", "html")
> (Pdb) p form
> FieldStorage(None, None, [])
> (Pdb) p form.keys()
> []
> 
> I can "fix" this by changing line 407 of tags.py from
> 
>     except AttributeError:
> 
> to
> 
>     except KeyError:
> 
> Now pyblosxom works as desired.  However, I don't understand what is going on with form.
> 
> Thanks again,
> Andrew
> 
> 
> % ./pyblosxom.cgi test
> pyblosxom.cgi version 1.5rc2 20100803
> Trying to import the config module....
> System Information
> ==================
> 
> - pyblosxom:    1.5rc2 20100803
> - sys.version:  2.5.1 (r251:54863, Feb  6 2009, 19:02:12)  [GCC 4.0.1
>   (Apple Inc. build 5465)]
> - os.name:      posix
> - codebase:     /Library/Python/2.5/site-
>   packages/pyblosxom-1.5rc2-py2.5.egg
> 
> Checking config.py file
> =======================
> - properties set: 20
> - datadir '/Users/adf/Sites/blog2/entries' exists.
> 
> Checking plugin configuration
> =============================
> - This goes through your plugins and asks each of them to verify
>   configuration and installation.
> 
> ----
> 
> The following plugins do not support installation verification:
> - 'rst' (/path/to/blog/plugins/entryparsers/rst.pyc)
> - 'tags' (/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py)
> 
> Verification complete.  Correct any errors and warnings above.
> 
> 
>> Date: Wed, 13 Oct 2010 09:52:30 -0400
>> From: wi...@bl...
>> To: afi...@ho...
>> CC: pyb...@li...
>> Subject: Re: [pyblosxom-users] Tag Fail
>>
>> Read through the troubleshooting part of the user manual and see if that
>> helps at all:
>>
>> http://pyblosxom.bluesock.org/1.5/deploy_cgi.html#trouble-shooting
>>
>> /will
>>
>>
>> On 10/13/2010 03:17 AM, andrew fitting wrote:
>>>
>>> Will,
>>>
>>> Thanks for your help.  The <string> errors are related to malformed rst files.  For now I've removed them and those errors are not there.  Now I get this.
>>>
>>> % pyblosxom-cmd buildtags --config=/path/to/blog/config.py
>>> pyblosxom-cmd version 1.5rc2 20100803
>>> Adding /path/blog/ to sys.path....
>>>
>>> There is now a tags.index file
>>>
>>> Then (as long as the tags plugin is enabled) I get
>>> A server error occurred.  Please contact the administrator.as a response from the cgi script.  Without it, I see blog posts.  The only thing I can think of is to try and renderurl and see what the errors are.  This is what I tried.  If you have any thoughts on why the form dictionary doesn't have a "flav" key, I'd be interested.
>>>
>>> Thanks,
>>> Andrew
>>>
>>> % pyblosxom-cmd renderurl --config=/path/to/blog/config.py "http://localhost/~me/blog/pyblosxom.cgi"
>>> pyblosxom-cmd version 1.5rc2 20100803
>>> Adding /Users/adf/Sites/blog/ to sys.path....
>>> Trying to import the config module....
>>> Traceback (most recent call last):
>>>   File "/usr/local/bin/pyblosxom-cmd", line 5, in <module>
>>>     pkg_resources.run_script('pyblosxom==1.5rc2', 'pyblosxom-cmd')
>>>   File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 448, in run_script
>>>     self.require(requires)[0].run_script(script_name, ns)
>>>   File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 1166, in run_script
>>>     execfile(script_filename, namespace, namespace)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/EGG-INFO/scripts/pyblosxom-cmd", line 25, in <module>
>>>     sys.exit(command_line_handler("pyblosxom-cmd", sys.argv))
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 431, in command_line_handler
>>>     return f(command, argv)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 311, in render_url
>>>     p.run_render_one(url, options.headers)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 238, in run_render_one
>>>     response = tools.render_url(config, url, query)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 979, in render_url
>>>     p.run(static=True)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 176, in run
>>>     blosxom_handler(self._request)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 936, in blosxom_handler
>>>     renderer.render()
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 316, in render
>>>     self.write(self.render_template(self.get_parse_vars(), "head"))
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 358, in render_template
>>>     {"entry": entry, "template": template})
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 384, in _run_callback
>>>     defaultfunc=lambda x:x)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 776, in run_callback
>>>     output = func(input)
>>>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py", line 406, in cb_head
>>>     flavour = form["flav"].value
>>>   File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/cgi.py", line 558, in __getitem__
>>>     raise KeyError, key
>>> KeyError: 'flav'
>>>
>>>
>>>
>>>> Date: Tue, 12 Oct 2010 11:50:18 -0400
>>>> From: wi...@bl...
>>>> To: afi...@ho...
>>>> CC: pyb...@li...
>>>> Subject: Re: [pyblosxom-users] Tag Fail
>>>>
>>>> I can't tell what it is you've copied and pasted here.  Can you copy and
>>>> paste the command line you used as well as the output?
>>>>
>>>> The <string>: lines indicate there's an eval somewhere.  So something
>>>> (probably unrelated to the tags plugin) isn't right.
>>>>
>>>>
>>>> On 10/12/2010 12:57 AM, andrew fitting wrote:
>>>>>
>>>>> Thanks for the response, Will.  I tried that and now I get a slightly different error
>>>>>
>>>>> pyblosxom-cmd version 1.5rc2 20100803
>>>>> Adding /path/to//blog/ to sys.path....
>>>>> <string>:28: (ERROR/3) Unknown interpreted text role "super".
>>>>> <string>:15: (ERROR/3) Unexpected indentation.
>>>>>
>>>>>
>>>>>
>>>>>> Date: Sun, 10 Oct 2010 08:33:13 -0400
>>>>>> From: wi...@bl...
>>>>>> To: afi...@ho...
>>>>>> CC: pyb...@li...
>>>>>> Subject: Re: [pyblosxom-users] Tag Fail
>>>>>>
>>>>>> You need to specify the config file on the command line because
>>>>>> otherwise pyblosxom-cmd doesn't know what pyblosxom blog you're talking
>>>>>> about.
>>>>>>
>>>>>> See the pyblosxom-cmd help for more details.
>>>>>>
>>>>>>
>>>>>> On 10/09/2010 05:10 PM, andrew fitting wrote:
>>>>>>>
>>>>>>> Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns
>>>>>>>
>>>>>>> pyblosxom-cmd version 1.5rc2 20100803
>>>>>>> Command 'buildtags' does not exist.
>>>>>>>     test           Tests installation and configuration for a blog.
>>>>>>>     create         Creates directory structure for a new blog.
>>>>>>>     staticrender   Statically renders your blog into an HTML site.
>>>>>>>     renderurl      Renders a single url of your blog.
>>>>>>>
>>>>>>> I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.
>>>>>>>
>>>>>>> Thanks
>>>>>  		 	   		  
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>>>> Spend less time writing and  rewriting code and more time creating great
>>>>> experiences on the web. Be a part of the beta today.
>>>>> http://p.sf.net/sfu/beautyoftheweb
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> pyblosxom-users mailing list
>>>>> pyb...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>>>  		 	   		  
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>>
>>>
>>>
>>> _______________________________________________
>>> pyblosxom-users mailing list
>>> pyb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>  		 	   		  
> 
> 
> 
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> 
> 
> 
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users

Re: [pyblosxom-users] Tag Fail

[andrew f. <afi...@ho...>]

Will,

Thanks for your continued support.  I did try most of what's there.  I'm attaching the results of pyblosxom.cgi to the end of this message.  The apache error_log shows the same trace that the previous pyblosxom-cmd does: a KeyError on form inside the cb_head function of tags.  In the debugger, form is a FieldStorage object with no keys.

Uncaught exception. Entering post mortem debugging
Running 'cont' or 'step' will restart the program
> /System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/cgi.py(558)__getitem__()
-> raise KeyError, key
(Pdb) u
> /Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py(408)cb_head()
-> flavour = config.get("default_flavour", "html")
(Pdb) p form
FieldStorage(None, None, [])
(Pdb) p form.keys()
[]

I can "fix" this by changing line 407 of tags.py from

    except AttributeError:

to

    except KeyError:

Now pyblosxom works as desired.  However, I don't understand what is going on with form.

Thanks again,
Andrew


% ./pyblosxom.cgi test
pyblosxom.cgi version 1.5rc2 20100803
Trying to import the config module....
System Information
==================

- pyblosxom:    1.5rc2 20100803
- sys.version:  2.5.1 (r251:54863, Feb  6 2009, 19:02:12)  [GCC 4.0.1
  (Apple Inc. build 5465)]
- os.name:      posix
- codebase:     /Library/Python/2.5/site-
  packages/pyblosxom-1.5rc2-py2.5.egg

Checking config.py file
=======================
- properties set: 20
- datadir '/Users/adf/Sites/blog2/entries' exists.

Checking plugin configuration
=============================
- This goes through your plugins and asks each of them to verify
  configuration and installation.

----

The following plugins do not support installation verification:
- 'rst' (/path/to/blog/plugins/entryparsers/rst.pyc)
- 'tags' (/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py)

Verification complete.  Correct any errors and warnings above.


> Date: Wed, 13 Oct 2010 09:52:30 -0400
> From: wi...@bl...
> To: afi...@ho...
> CC: pyb...@li...
> Subject: Re: [pyblosxom-users] Tag Fail
> 
> Read through the troubleshooting part of the user manual and see if that
> helps at all:
> 
> http://pyblosxom.bluesock.org/1.5/deploy_cgi.html#trouble-shooting
> 
> /will
> 
> 
> On 10/13/2010 03:17 AM, andrew fitting wrote:
> > 
> > Will,
> > 
> > Thanks for your help.  The <string> errors are related to malformed rst files.  For now I've removed them and those errors are not there.  Now I get this.
> > 
> > % pyblosxom-cmd buildtags --config=/path/to/blog/config.py
> > pyblosxom-cmd version 1.5rc2 20100803
> > Adding /path/blog/ to sys.path....
> > 
> > There is now a tags.index file
> > 
> > Then (as long as the tags plugin is enabled) I get
> > A server error occurred.  Please contact the administrator.as a response from the cgi script.  Without it, I see blog posts.  The only thing I can think of is to try and renderurl and see what the errors are.  This is what I tried.  If you have any thoughts on why the form dictionary doesn't have a "flav" key, I'd be interested.
> > 
> > Thanks,
> > Andrew
> > 
> > % pyblosxom-cmd renderurl --config=/path/to/blog/config.py "http://localhost/~me/blog/pyblosxom.cgi"
> > pyblosxom-cmd version 1.5rc2 20100803
> > Adding /Users/adf/Sites/blog/ to sys.path....
> > Trying to import the config module....
> > Traceback (most recent call last):
> >   File "/usr/local/bin/pyblosxom-cmd", line 5, in <module>
> >     pkg_resources.run_script('pyblosxom==1.5rc2', 'pyblosxom-cmd')
> >   File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 448, in run_script
> >     self.require(requires)[0].run_script(script_name, ns)
> >   File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 1166, in run_script
> >     execfile(script_filename, namespace, namespace)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/EGG-INFO/scripts/pyblosxom-cmd", line 25, in <module>
> >     sys.exit(command_line_handler("pyblosxom-cmd", sys.argv))
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 431, in command_line_handler
> >     return f(command, argv)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 311, in render_url
> >     p.run_render_one(url, options.headers)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 238, in run_render_one
> >     response = tools.render_url(config, url, query)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 979, in render_url
> >     p.run(static=True)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 176, in run
> >     blosxom_handler(self._request)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 936, in blosxom_handler
> >     renderer.render()
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 316, in render
> >     self.write(self.render_template(self.get_parse_vars(), "head"))
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 358, in render_template
> >     {"entry": entry, "template": template})
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 384, in _run_callback
> >     defaultfunc=lambda x:x)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 776, in run_callback
> >     output = func(input)
> >   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py", line 406, in cb_head
> >     flavour = form["flav"].value
> >   File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/cgi.py", line 558, in __getitem__
> >     raise KeyError, key
> > KeyError: 'flav'
> > 
> > 
> > 
> >> Date: Tue, 12 Oct 2010 11:50:18 -0400
> >> From: wi...@bl...
> >> To: afi...@ho...
> >> CC: pyb...@li...
> >> Subject: Re: [pyblosxom-users] Tag Fail
> >>
> >> I can't tell what it is you've copied and pasted here.  Can you copy and
> >> paste the command line you used as well as the output?
> >>
> >> The <string>: lines indicate there's an eval somewhere.  So something
> >> (probably unrelated to the tags plugin) isn't right.
> >>
> >>
> >> On 10/12/2010 12:57 AM, andrew fitting wrote:
> >>>
> >>> Thanks for the response, Will.  I tried that and now I get a slightly different error
> >>>
> >>> pyblosxom-cmd version 1.5rc2 20100803
> >>> Adding /path/to//blog/ to sys.path....
> >>> <string>:28: (ERROR/3) Unknown interpreted text role "super".
> >>> <string>:15: (ERROR/3) Unexpected indentation.
> >>>
> >>>
> >>>
> >>>> Date: Sun, 10 Oct 2010 08:33:13 -0400
> >>>> From: wi...@bl...
> >>>> To: afi...@ho...
> >>>> CC: pyb...@li...
> >>>> Subject: Re: [pyblosxom-users] Tag Fail
> >>>>
> >>>> You need to specify the config file on the command line because
> >>>> otherwise pyblosxom-cmd doesn't know what pyblosxom blog you're talking
> >>>> about.
> >>>>
> >>>> See the pyblosxom-cmd help for more details.
> >>>>
> >>>>
> >>>> On 10/09/2010 05:10 PM, andrew fitting wrote:
> >>>>>
> >>>>> Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns
> >>>>>
> >>>>> pyblosxom-cmd version 1.5rc2 20100803
> >>>>> Command 'buildtags' does not exist.
> >>>>>     test           Tests installation and configuration for a blog.
> >>>>>     create         Creates directory structure for a new blog.
> >>>>>     staticrender   Statically renders your blog into an HTML site.
> >>>>>     renderurl      Renders a single url of your blog.
> >>>>>
> >>>>> I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.
> >>>>>
> >>>>> Thanks
> >>>  		 	   		  
> >>>
> >>>
> >>>
> >>> ------------------------------------------------------------------------------
> >>> Beautiful is writing same markup. Internet Explorer 9 supports
> >>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> >>> Spend less time writing and  rewriting code and more time creating great
> >>> experiences on the web. Be a part of the beta today.
> >>> http://p.sf.net/sfu/beautyoftheweb
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> pyblosxom-users mailing list
> >>> pyb...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
> >  		 	   		  
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Beautiful is writing same markup. Internet Explorer 9 supports
> > standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> > Spend less time writing and  rewriting code and more time creating great
> > experiences on the web. Be a part of the beta today.
> > http://p.sf.net/sfu/beautyoftheweb
> > 
> > 
> > 
> > _______________________________________________
> > pyblosxom-users mailing list
> > pyb...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
 		 	   		  

Re: [pyblosxom-users] Tag Fail

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

Read through the troubleshooting part of the user manual and see if that
helps at all:

http://pyblosxom.bluesock.org/1.5/deploy_cgi.html#trouble-shooting

/will


On 10/13/2010 03:17 AM, andrew fitting wrote:
> 
> Will,
> 
> Thanks for your help.  The <string> errors are related to malformed rst files.  For now I've removed them and those errors are not there.  Now I get this.
> 
> % pyblosxom-cmd buildtags --config=/path/to/blog/config.py
> pyblosxom-cmd version 1.5rc2 20100803
> Adding /path/blog/ to sys.path....
> 
> There is now a tags.index file
> 
> Then (as long as the tags plugin is enabled) I get
> A server error occurred.  Please contact the administrator.as a response from the cgi script.  Without it, I see blog posts.  The only thing I can think of is to try and renderurl and see what the errors are.  This is what I tried.  If you have any thoughts on why the form dictionary doesn't have a "flav" key, I'd be interested.
> 
> Thanks,
> Andrew
> 
> % pyblosxom-cmd renderurl --config=/path/to/blog/config.py "http://localhost/~me/blog/pyblosxom.cgi"
> pyblosxom-cmd version 1.5rc2 20100803
> Adding /Users/adf/Sites/blog/ to sys.path....
> Trying to import the config module....
> Traceback (most recent call last):
>   File "/usr/local/bin/pyblosxom-cmd", line 5, in <module>
>     pkg_resources.run_script('pyblosxom==1.5rc2', 'pyblosxom-cmd')
>   File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 448, in run_script
>     self.require(requires)[0].run_script(script_name, ns)
>   File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 1166, in run_script
>     execfile(script_filename, namespace, namespace)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/EGG-INFO/scripts/pyblosxom-cmd", line 25, in <module>
>     sys.exit(command_line_handler("pyblosxom-cmd", sys.argv))
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 431, in command_line_handler
>     return f(command, argv)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 311, in render_url
>     p.run_render_one(url, options.headers)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 238, in run_render_one
>     response = tools.render_url(config, url, query)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 979, in render_url
>     p.run(static=True)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 176, in run
>     blosxom_handler(self._request)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 936, in blosxom_handler
>     renderer.render()
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 316, in render
>     self.write(self.render_template(self.get_parse_vars(), "head"))
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 358, in render_template
>     {"entry": entry, "template": template})
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 384, in _run_callback
>     defaultfunc=lambda x:x)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 776, in run_callback
>     output = func(input)
>   File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py", line 406, in cb_head
>     flavour = form["flav"].value
>   File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/cgi.py", line 558, in __getitem__
>     raise KeyError, key
> KeyError: 'flav'
> 
> 
> 
>> Date: Tue, 12 Oct 2010 11:50:18 -0400
>> From: wi...@bl...
>> To: afi...@ho...
>> CC: pyb...@li...
>> Subject: Re: [pyblosxom-users] Tag Fail
>>
>> I can't tell what it is you've copied and pasted here.  Can you copy and
>> paste the command line you used as well as the output?
>>
>> The <string>: lines indicate there's an eval somewhere.  So something
>> (probably unrelated to the tags plugin) isn't right.
>>
>>
>> On 10/12/2010 12:57 AM, andrew fitting wrote:
>>>
>>> Thanks for the response, Will.  I tried that and now I get a slightly different error
>>>
>>> pyblosxom-cmd version 1.5rc2 20100803
>>> Adding /path/to//blog/ to sys.path....
>>> <string>:28: (ERROR/3) Unknown interpreted text role "super".
>>> <string>:15: (ERROR/3) Unexpected indentation.
>>>
>>>
>>>
>>>> Date: Sun, 10 Oct 2010 08:33:13 -0400
>>>> From: wi...@bl...
>>>> To: afi...@ho...
>>>> CC: pyb...@li...
>>>> Subject: Re: [pyblosxom-users] Tag Fail
>>>>
>>>> You need to specify the config file on the command line because
>>>> otherwise pyblosxom-cmd doesn't know what pyblosxom blog you're talking
>>>> about.
>>>>
>>>> See the pyblosxom-cmd help for more details.
>>>>
>>>>
>>>> On 10/09/2010 05:10 PM, andrew fitting wrote:
>>>>>
>>>>> Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns
>>>>>
>>>>> pyblosxom-cmd version 1.5rc2 20100803
>>>>> Command 'buildtags' does not exist.
>>>>>     test           Tests installation and configuration for a blog.
>>>>>     create         Creates directory structure for a new blog.
>>>>>     staticrender   Statically renders your blog into an HTML site.
>>>>>     renderurl      Renders a single url of your blog.
>>>>>
>>>>> I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.
>>>>>
>>>>> Thanks
>>>  		 	   		  
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>>
>>>
>>>
>>> _______________________________________________
>>> pyblosxom-users mailing list
>>> pyb...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>  		 	   		  
> 
> 
> 
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> 
> 
> 
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users

Re: [pyblosxom-users] Tag Fail

[andrew f. <afi...@ho...>]

Will,

Thanks for your help.  The <string> errors are related to malformed rst files.  For now I've removed them and those errors are not there.  Now I get this.

% pyblosxom-cmd buildtags --config=/path/to/blog/config.py
pyblosxom-cmd version 1.5rc2 20100803
Adding /path/blog/ to sys.path....

There is now a tags.index file

Then (as long as the tags plugin is enabled) I get
A server error occurred.  Please contact the administrator.as a response from the cgi script.  Without it, I see blog posts.  The only thing I can think of is to try and renderurl and see what the errors are.  This is what I tried.  If you have any thoughts on why the form dictionary doesn't have a "flav" key, I'd be interested.

Thanks,
Andrew

% pyblosxom-cmd renderurl --config=/path/to/blog/config.py "http://localhost/~me/blog/pyblosxom.cgi"
pyblosxom-cmd version 1.5rc2 20100803
Adding /Users/adf/Sites/blog/ to sys.path....
Trying to import the config module....
Traceback (most recent call last):
  File "/usr/local/bin/pyblosxom-cmd", line 5, in <module>
    pkg_resources.run_script('pyblosxom==1.5rc2', 'pyblosxom-cmd')
  File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 448, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/opt/local/lib/python2.5/site-packages/pkg_resources.py", line 1166, in run_script
    execfile(script_filename, namespace, namespace)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/EGG-INFO/scripts/pyblosxom-cmd", line 25, in <module>
    sys.exit(command_line_handler("pyblosxom-cmd", sys.argv))
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 431, in command_line_handler
    return f(command, argv)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/commandline.py", line 311, in render_url
    p.run_render_one(url, options.headers)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 238, in run_render_one
    response = tools.render_url(config, url, query)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 979, in render_url
    p.run(static=True)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 176, in run
    blosxom_handler(self._request)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/pyblosxom.py", line 936, in blosxom_handler
    renderer.render()
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 316, in render
    self.write(self.render_template(self.get_parse_vars(), "head"))
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 358, in render_template
    {"entry": entry, "template": template})
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/renderers/blosxom.py", line 384, in _run_callback
    defaultfunc=lambda x:x)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/Pyblosxom/tools.py", line 776, in run_callback
    output = func(input)
  File "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags/tags.py", line 406, in cb_head
    flavour = form["flav"].value
  File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/cgi.py", line 558, in __getitem__
    raise KeyError, key
KeyError: 'flav'



> Date: Tue, 12 Oct 2010 11:50:18 -0400
> From: wi...@bl...
> To: afi...@ho...
> CC: pyb...@li...
> Subject: Re: [pyblosxom-users] Tag Fail
> 
> I can't tell what it is you've copied and pasted here.  Can you copy and
> paste the command line you used as well as the output?
> 
> The <string>: lines indicate there's an eval somewhere.  So something
> (probably unrelated to the tags plugin) isn't right.
> 
> 
> On 10/12/2010 12:57 AM, andrew fitting wrote:
> > 
> > Thanks for the response, Will.  I tried that and now I get a slightly different error
> > 
> > pyblosxom-cmd version 1.5rc2 20100803
> > Adding /path/to//blog/ to sys.path....
> > <string>:28: (ERROR/3) Unknown interpreted text role "super".
> > <string>:15: (ERROR/3) Unexpected indentation.
> > 
> > 
> > 
> >> Date: Sun, 10 Oct 2010 08:33:13 -0400
> >> From: wi...@bl...
> >> To: afi...@ho...
> >> CC: pyb...@li...
> >> Subject: Re: [pyblosxom-users] Tag Fail
> >>
> >> You need to specify the config file on the command line because
> >> otherwise pyblosxom-cmd doesn't know what pyblosxom blog you're talking
> >> about.
> >>
> >> See the pyblosxom-cmd help for more details.
> >>
> >>
> >> On 10/09/2010 05:10 PM, andrew fitting wrote:
> >>>
> >>> Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns
> >>>
> >>> pyblosxom-cmd version 1.5rc2 20100803
> >>> Command 'buildtags' does not exist.
> >>>     test           Tests installation and configuration for a blog.
> >>>     create         Creates directory structure for a new blog.
> >>>     staticrender   Statically renders your blog into an HTML site.
> >>>     renderurl      Renders a single url of your blog.
> >>>
> >>> I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.
> >>>
> >>> Thanks
> >  		 	   		  
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Beautiful is writing same markup. Internet Explorer 9 supports
> > standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> > Spend less time writing and  rewriting code and more time creating great
> > experiences on the web. Be a part of the beta today.
> > http://p.sf.net/sfu/beautyoftheweb
> > 
> > 
> > 
> > _______________________________________________
> > pyblosxom-users mailing list
> > pyb...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
 		 	   		  

Re: [pyblosxom-users] Tag Fail

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

I can't tell what it is you've copied and pasted here.  Can you copy and
paste the command line you used as well as the output?

The <string>: lines indicate there's an eval somewhere.  So something
(probably unrelated to the tags plugin) isn't right.


On 10/12/2010 12:57 AM, andrew fitting wrote:
> 
> Thanks for the response, Will.  I tried that and now I get a slightly different error
> 
> pyblosxom-cmd version 1.5rc2 20100803
> Adding /path/to//blog/ to sys.path....
> <string>:28: (ERROR/3) Unknown interpreted text role "super".
> <string>:15: (ERROR/3) Unexpected indentation.
> 
> 
> 
>> Date: Sun, 10 Oct 2010 08:33:13 -0400
>> From: wi...@bl...
>> To: afi...@ho...
>> CC: pyb...@li...
>> Subject: Re: [pyblosxom-users] Tag Fail
>>
>> You need to specify the config file on the command line because
>> otherwise pyblosxom-cmd doesn't know what pyblosxom blog you're talking
>> about.
>>
>> See the pyblosxom-cmd help for more details.
>>
>>
>> On 10/09/2010 05:10 PM, andrew fitting wrote:
>>>
>>> Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns
>>>
>>> pyblosxom-cmd version 1.5rc2 20100803
>>> Command 'buildtags' does not exist.
>>>     test           Tests installation and configuration for a blog.
>>>     create         Creates directory structure for a new blog.
>>>     staticrender   Statically renders your blog into an HTML site.
>>>     renderurl      Renders a single url of your blog.
>>>
>>> I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.
>>>
>>> Thanks
>  		 	   		  
> 
> 
> 
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> 
> 
> 
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users

Re: [pyblosxom-users] Tag Fail

[andrew f. <afi...@ho...>]

Asheesh,

Sure...




# -*- coding: utf-8 -*-
# =============================================================
# This is the config file for PyBlosxom.  You should go through 
# the file and fill in values for the various properties.  This 
# affects the behavior of your blog.
#
# The PyBlosxom documentation has additional information on 
# configuration variables.
# =============================================================

# Don't touch this next line.
py = {}


# Codebase configuration
# ======================

# If you did not install PyBlosxom as a library (i.e. python setup.py install)
# then uncomment this next line and point it to your PyBlosxom installation
# directory.
# Note, this should be the directory that holds the "Pyblosxom" 
# directory (note the case--uppercase P lowercase b!).
#py["codebase"] = "/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg"

import os

blogdir = "/path/to/blog/"

# Blog configuration
# ==================

# What is the title of this blog?
py["blog_title"] = "Andrew's Stuff"

# What is the description of this blog?
py["blog_description"] = "Journaling"

# Who are the author(s) of this blog?
py["blog_author"] = "Andrew"

# What is the email address through which readers of the blog may contact
# the authors?
py["blog_email"] = "em...@ex..."

# These are the rights you give to others in regards to the content
# on your blog.  Generally, this is the copyright information.
# This is used in the Atom feeds.  Leaving this blank or not filling
# it in correctly could result in a feed that doesn't validate.
py["blog_rights"] = "Copyright 2005 Joe Bobb"

# What is this blog's primary language (for outgoing RSS feed)?
py["blog_language"] = "en"

# Encoding for output.  This defaults to utf-8.
py["blog_encoding"] = "utf-8"

# What is the locale for this blog?  This is used when formatting dates
# and other locale-sensitive things.  Make sure the locale is valid for
# your system.  See the PyBlosxom documentation for details.
#py["locale"] = "en_US.iso-8859-1"

# Where are this blog's entries kept?
py["datadir"] = os.path.join(blogdir, "entries")

# Where are this blog's flavours kept?
py["flavourdir"] = os.path.join(blogdir, "flavours")

# List of strings with directories that should be ignored (e.g. "CVS")
# ex: py['ignore_directories'] = ["CVS", "temp"]
py["ignore_directories"] = []

# Should I stick only to the datadir for items or travel down the directory
# hierarchy looking for items?  If so, to what depth?
# 0 = infinite depth (aka grab everything)
# 1 = datadir only
# n = n levels down
py["depth"] = 0

# How many entries should I show on the home page and category pages?
# If you put 0 here, then I will show all pages.
# Note: this doesn't affect date-based archive pages.
py["num_entries"] = 5

# What is the default flavour you want to use when the user doesn't
# specify a flavour in the request?
py["default_flavour"] = "adf"



# Logging configuration
# =====================

# Where should PyBlosxom write logged messages to?
# If set to "NONE" log messages are silently ignored.
# Falls back to sys.stderr if the file can't be opened for writing.
#py["log_file"] = os.path.join(blogdir, "logs", "pyblosxom.log")

# At what level should we log to log_file?
# One of: "critical", "error", "warning", "info", "debug"
# For production, "warning" or "error' is recommended.
#py["log_level"] = "warning"

# This lets you specify which channels should be logged.
# If specified, only messages from the listed channels are logged.
# Each plugin logs to it's own channel, therefor channelname == pluginname.
# Application level messages are logged to a channel named "root".
# If you use log_filter and ommit the "root" channel here, app level messages 
# are not logged! log_filter is mainly interesting to debug a specific plugin.
#py["log_filter"] = ["root", "plugin1", "plugin2"]



# Plugin configuration
# ====================

# Plugin directories:
# You can now specify where you plugins all lives, there are two types
# of plugindirectories, the standard pyblosxom plugins, and the xmlrpc
# plugins.  You can list out as many directories you want, but they
# should only contain the related plugins.
# Example: py['plugin_dirs'] = [ "/home/joe/blog/plugins",
#                                "/var/lib/pyblosxom/plugins" ]
py["plugin_dirs"] = [os.path.join(blogdir, "plugins"),os.path.join(blogdir, "plugins", "entryparsers"),"/Library/Python/2.5/site-packages/pyblosxom-1.5rc2-py2.5.egg/plugins/tags"]

# There are two ways for PyBlosxom to load plugins.  The first is the
# default way which involves loading all the plugins in the lib/plugins
# directory in alphanumeric order.  The second is by specifying a
# "load_plugins" key here.  Doing so will cause us to load only the
# plugins you name and we will load them in the order you name them.
# The "load_plugins" key is a list of strings where each string is
# the name of a plugin module (i.e. the filename without the .py at
# the end).
# If you specify an empty list, then this will load no plugins.
# ex: py["load_plugins"] = ["pycalendar", "pyfortune", "pyarchives"]
py["load_plugins"] = ["rst","tags"]



# ======================
# Optional Configuration
# ======================

# What should this blog use as its base url?
#py["base_url"] = "http://www.example.com/weblog"

# Default parser/preformatter. Defaults to plain (does nothing)
#py["parser"] = "plain"



# Caching configuration
# =====================

# Using Caching? Caching speeds up rendering the page that is going to be
# shown. Even if you are not using pyblosxom special features, caching can
# improve rendering speed of certain flavours that can show a large number of
# files at one time. Choose a cache mechanism you'd like, see the
# Pyblosxom/cache/ directory, and read the source on how to enable caching with
# the particular cache driver, you need to set two variables:
#py["cacheDriver"] = "xxxx"
#py["cacheConfig"] = ""



# Static rendering
# ================

# Doing static rendering?  Static rendering essentially "compiles" your
# blog into a series of static html pages.  For more details, see the
# documentation.
# 
# What directory do you want your static html pages to go into?
#py["static_dir"] = ""

# What flavours should get generated?
#py["static_flavours"] = ["html"]

# What other paths should we statically render?
# This is for additional urls handled by other plugins like the booklist
# and plugin_info plugins.  If there are multiple flavours you want
# to capture, specify each:
# ex: py["static_urls"] = ["/booklist.rss", "/booklist.html"]
#py["static_urls"] = ["/path/to/url1", "/path/to/url2"]

# Whether (1) or not (0) you want to create date indexes using month
# names?  (ex. /2004/Apr/01)  Defaults to 1 (yes).
#py["static_monthnames"] = 1

# Whether (1) or not (0) you want to create date indexes using month
# numbers?  (ex. /2004/04/01)  Defaults to 0 (no).
#py["static_monthnumbers"] = 0


> Date: Tue, 12 Oct 2010 01:36:27 -0400
> From: as...@as...
> To: pyb...@li...
> Subject: Re: [pyblosxom-users] Tag Fail
> 
> On Tue, 12 Oct 2010, andrew fitting wrote:
> 
> > Thanks for the response, Will.  I tried that and now I get a slightly 
> > different error
> 
> I haven't used pyblosxom-cmd but maybe it doesn't like your config file. 
> Can you attach it in a response?
> 
> -- Asheesh.
> 
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
 		 	   		  

Re: [pyblosxom-users] Tag Fail

[Asheesh L. <as...@as...>]

On Tue, 12 Oct 2010, andrew fitting wrote:

> Thanks for the response, Will.  I tried that and now I get a slightly 
> different error

I haven't used pyblosxom-cmd but maybe it doesn't like your config file. 
Can you attach it in a response?

-- Asheesh.

Re: [pyblosxom-users] Tag Fail

[andrew f. <afi...@ho...>]

Thanks for the response, Will.  I tried that and now I get a slightly different error

pyblosxom-cmd version 1.5rc2 20100803
Adding /path/to//blog/ to sys.path....
<string>:28: (ERROR/3) Unknown interpreted text role "super".
<string>:15: (ERROR/3) Unexpected indentation.



> Date: Sun, 10 Oct 2010 08:33:13 -0400
> From: wi...@bl...
> To: afi...@ho...
> CC: pyb...@li...
> Subject: Re: [pyblosxom-users] Tag Fail
> 
> You need to specify the config file on the command line because
> otherwise pyblosxom-cmd doesn't know what pyblosxom blog you're talking
> about.
> 
> See the pyblosxom-cmd help for more details.
> 
> 
> On 10/09/2010 05:10 PM, andrew fitting wrote:
> > 
> > Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns
> > 
> > pyblosxom-cmd version 1.5rc2 20100803
> > Command 'buildtags' does not exist.
> >     test           Tests installation and configuration for a blog.
> >     create         Creates directory structure for a new blog.
> >     staticrender   Statically renders your blog into an HTML site.
> >     renderurl      Renders a single url of your blog.
> > 
> > I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.
> > 
> > Thanks
 		 	   		  

[pyblosxom-users] Unsubscribe

[Fernando E. <com...@gm...>]

Unsubscribe
 On Sep 27, 2010 4:50 PM, <pyb...@li...>
wrote:
> Send pyblosxom-users mailing list submissions to
> pyb...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
> or, via email, send a message with subject or body 'help' to
> pyb...@li...
>
> You can reach the person managing the list at
> pyb...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pyblosxom-users digest..."

Re: [pyblosxom-users] Tag Fail

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

You need to specify the config file on the command line because
otherwise pyblosxom-cmd doesn't know what pyblosxom blog you're talking
about.

See the pyblosxom-cmd help for more details.


On 10/09/2010 05:10 PM, andrew fitting wrote:
> 
> Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns
> 
> pyblosxom-cmd version 1.5rc2 20100803
> Command 'buildtags' does not exist.
>     test           Tests installation and configuration for a blog.
>     create         Creates directory structure for a new blog.
>     staticrender   Statically renders your blog into an HTML site.
>     renderurl      Renders a single url of your blog.
> 
> I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.
> 
> Thanks

[pyblosxom-users] Tag Fail

[andrew f. <afi...@ho...>]

Overall, pyblosxom is working pretty well for me with one exception: tags.  The command "pyblosxom-cmd buildtags" always returns

pyblosxom-cmd version 1.5rc2 20100803
Command 'buildtags' does not exist.
    test           Tests installation and configuration for a blog.
    create         Creates directory structure for a new blog.
    staticrender   Statically renders your blog into an HTML site.
    renderurl      Renders a single url of your blog.

I have the install's "pyblosxom-1.5rc2-py2.5.egg/plugins/tags/" on my "plugin_dirs" and the "tags" plugin in "load_plugins".  I've tried a couple other variations but none make any difference.  I'm obviously missing something obvious but can't figure out what it is. Any suggestions would be appreciated.

Thanks
 		 	   		  

Re: [pyblosxom-users] pyblosxom 1.5rc2 released!

[seanh <sn...@gm...>]

On Tue, Sep 28, 2010 at 01:15:04AM +0000, Will Kahn-Greene wrote:
> 4. You couldn't get it to work with virtualenv.  It sounds like you
> missed a step when setting up the virtual environment.
> Incidentally, using virtual environments makes it really easy to
> encapsulate PyBlosxom and it's dependencies into a directory that
> you can wipe away if you don't want it around anymore.  Then it
> doesn't poison your system.  Also, when you upgrade system packages,
> PyBlosxom won't break.

I returned to the virtualenv instructions today. I don't understand step
4:

http://pyblosxom.bluesock.org/1.5/notes/INSTALL.html#installing-pyblosxom-to-hack-on-it

which says: `easy_install paste_deploy` or `pip install paste_deploy`.
How are either of those commands going to know that I mean to install
into the virtual environment that I've just created? Surely there is an
instruction missing? I cd'd into the bin/ dir in my virtual environment
and saw that it contains easy_install and pip executables so I tried
executing the commands using those executables, but they don't seem to
think that "paste_deploy" exists:

seanh@kisimul:.../foo/VEDIR/bin % ./easy_install paste_deploy
Searching for paste-deploy
Reading http://pypi.python.org/simple/paste_deploy/
Reading http://pypi.python.org/simple/paste-deploy/
Couldn't find index page for 'paste_deploy' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading http://pypi.python.org/simple/
No local packages or download links found for paste-deploy
error: Could not find suitable distribution for Requirement.parse('paste-deploy')
seanh@kisimul:.../VEDIR/bin % (1) ./pip install paste_deploy
Downloading/unpacking paste-deploy
  Could not find any downloads that satisfy the requirement paste-deploy
No distributions at all found for paste-deploy
Storing complete log in /home/seanh/.pip/pip.log
seanh@kisimul:.../VEDIR/bin % (1) 

Also, the note at the top of the Installing PyBlosxom page in the docs
says "If you’re testing PyBlosxom, use virtualenv and deploy with Paste"
but instructions to do so do not follow. They are further down the page,
and with a different title "Installing PyBlosxom to hack on it". The
note at the top of the page does not lead the reader to this subsection.

Re: [pyblosxom-users] pyblosxom 1.5rc2 released!

[seanh <sn...@gm...>]

On Tue, Sep 28, 2010 at 01:15:04AM +0000, Will Kahn-Greene wrote:
> 
> So let's work through your issues one at a time:
> 
> 1. The INSTALL file is different than the instructions on the
> web-site. That's because I did the 1.5rc2 release and then we did
> some documentation changes which I pushed to the web-site.  The
> changes should be persisted in git, but they haven't made it to a
> release tarball yet.

Right. So the instructions on the site are the newest ones.

> It's also possible that you were looking at the wrong site.  Were
> you looking at the instructions on http://pyblosxom.bluesock.org/ or
> http://pyblosxom.sourceforge.net/ ?

No, it was bluesock.org.

> 4. You couldn't get it to work with virtualenv.  It sounds like you
> missed a step when setting up the virtual environment.
> Incidentally, using virtual environments makes it really easy to
> encapsulate PyBlosxom and it's dependencies into a directory that
> you can wipe away if you don't want it around anymore.

That's good to know about. I'll have to learn my way around virtualenv
for the future.

> 5. You've now got a situation where you don't know what you've got
> on your system.  Ubuntu packages Python 2.6 such that all site
> packages are stored in the same place (might be dist packages--I
> know they changed the name between Python 2.5 and 2.6, but I don't
> remember the details offhand). Find that directory and you can just
> delete the pyblosxom related directory trees.  Then it won't be on
> your system anymore.

Great, thanks! Now I no how to clean up after python installers.

Haven't had time to return to trying to install pyblosxom yet. I thought
I'd try Jekyll instead, it is easy to install after all, just a simple
gem install ARGH! :)

> If anyone has any ideas on how to alleviate the confusion in the
> installation instructions, I'm interested in hearing them.  The
> source for the instructions is the INSTALL file in the git
> repository.

Sorry that I don't have time to work on the docs, but I will give my
thoughts.

Try not to duplicate instructions because they might go out of sync,
e.g. by having an INSTALL file and also install instructions on the
website.

The two notes at the top of the Installing PyBlosxom section in the docs
are insufficient. This is the version of the docs I'm talking about:

http://pyblosxom.bluesock.org/1.5/notes/INSTALL.html

Here's what I would do to it:

I think the Installing PyBlosxom section and subsections and the various
Deploying PyBlosxom sections and the upgrading pyblosxom section
probably need to be merged, they should each become subsections of one
big installing and deploying page. They have some overlap I think (e.g.
virtualenv and paste),  and the difference between 'installing' and
'deploying' is not obvious, if they were merged into one section then
that section could explain the difference at the top and contain all the
info on one page instead of spread about. I would suggest the following
headings:

Section: Installing and Deploying PyBlosxom
Subsection: Installing PyBlosxom on Your Computer
Subsubsection: Installing PyBlosxom with virtualenv and paste
Subsubsection: Upgrading PyBlosxom with virtualenv and paste
Subsubsection: Installing PyBlosxom with distribute and pip
Subsubsection: Upgrading PyBlosxom with distribute and pip
Subsubsection: Installing PyBlosxom with setuptools and easy_install
Subsubsection: Upgrading PyBlosxom with setuptools and easy_install
Subsection: Deploying PyBlosxom to a Web Server
The various subsubsections about the different ways of deploying.

At the top of "Section: Installing and Deploying PyBlosxom" explain the
difference between "Installing PyBlosxom on Your Computer" and
"Deploying PyBlosxom to a Web Server".

At the top of "Subsection: Installing PyBlosxom on Your Computer" add a
paragraph explaining why there are multiple ways of installing pyblosxom
on your computer, and some advice to the user about which they should
choose.  This should be in the form of an explanatory paragraph, an
introduction to the section, currently there is a brief note saying
virtualenv is easiest (and the instructions for virtualenv are elsewhere
in a different section!). This is what I think it should explain: from
what I now understand there are three ways to install: with virtualenv
and paste, with distribute and pip, or with setuptools and easy_install.
New users who just want to try out PyBlosxom and people who want to hack
on PyBlosxom want to use virtualenv because it's easy to undo, it should
say this right at the top of the section, and then the first subsection
in the section should be the one that tells you how to install with
virtualenv. Then, after trying PyBlosxom and deciding you want to use
it, if you need to install it on your system you can do so with either
distribute and pip or with setuptools and easy_install.  There are two
ways to install because Python, unfortunately, currently has two
incompatible packaging systems.  Warning: Choose one or the other, but
don't try both as they will conflict with each other. Then the
subsections about virtualenv, distribute and pip, and setuptools and
easy_install would follow.

In the subsubsections about each way of installing, explain briefly and
in general terms what the install commands do. I know you won't be able
to give exact details as it varies from system to system, but something
like "it installs files to a specific place, e.g.
/path/to/dist-packages on Ubuntu", would be a good idea, just so these
commands seem less like sorcery and the user has at least a starting
point if they need to debug or undo something.

Hope that helps anyone who might do some work on the docs!