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

Re: [pyblosxom-users] Spam on trackbacks (Was: 1.5 comment_draft_ext?)

[Blake W. <bw...@la...>]

  On 09/28/2010 11:07 AM, Joseph Reagle wrote:
> On Tuesday, September 28, 2010, will kahn-greene wrote:
>> I use it, so, yes.  Why do you ask?  Are you encountering problems with it?
> comments/README doesn't mention it and I haven't gotten it right yet in the upgrade, but working on it.
>
> A long time ago I had ping and trackbacks, but too much of it was spam -- trying to game Google rank. Do the new spam features like akismetcomments.py and check_javascript.py work for these too?

I found that most of my spam comments were on articles that were older 
than 30 days, so I whipped up the noOldComments plugin, which you can 
find at http://bwinton.latte.ca/temp/noOldComments.py

I know, it seems stupid that something so simple would block 98% of my 
spam comments, but there you go.  :)

Later,
Blake.

[pyblosxom-users] <div class="blosxomComments">

[Joseph R. <jos...@re...>]

So I continue to try the migration and my HTML is presently broken.

comment-story.html has a single open tag:
  <div class="blosxomComments">

This is necessary for a story+comments page, and is closed at the very end of comment-form.html .

However, I'm trying to get this to work with pyblosxom-1.5 and while it works on a comments+form page, a story view (e.g., http://reagle.org/joseph/blog2/ ) has these <div class="blosxomComments"> throughout the page. In my 1.4.3 install it doesn't appear content from comment-story.html makes it into the non-comment views....?

Re: [pyblosxom-users] Spam on trackbacks (Was: 1.5 comment_draft_ext?)

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

According to the documentation, akismetcomments works on comments and
trackbacks.

check_javascript probably doesn't help with spam from pingbacks and
trackbacks.  I don't know if they work with pingbacks and trackbacks,
either.

I don't use pingbacks, trackbacks, check_javascript or akismetcomments
on my blog, so I don't know.

I do use comment_draft_ext and it works fine.  I have it set like this
in my config.py file:

    py["comment_draft_ext"] = "cmt-"

/will


On 09/28/2010 11:07 AM, Joseph Reagle wrote:
> On Tuesday, September 28, 2010, will kahn-greene wrote:
>> I use it, so, yes.  Why do you ask?  Are you encountering problems with it?
> 
> comments/README doesn't mention it and I haven't gotten it right yet in the upgrade, but working on it.
> 
> A long time ago I had ping and trackbacks, but too much of it was spam -- trying to game Google rank. Do the new spam features like akismetcomments.py and check_javascript.py work for these too?
> 

[pyblosxom-users] Spam on trackbacks (Was: 1.5 comment_draft_ext?)

[Joseph R. <jos...@re...>]

On Tuesday, September 28, 2010, will kahn-greene wrote:
> I use it, so, yes.  Why do you ask?  Are you encountering problems with it?

comments/README doesn't mention it and I haven't gotten it right yet in the upgrade, but working on it.

A long time ago I had ping and trackbacks, but too much of it was spam -- trying to game Google rank. Do the new spam features like akismetcomments.py and check_javascript.py work for these too?

[pyblosxom-users] 1.5 comment_draft_ext?

[Joseph R. <jos...@re...>]

Is comment_draft_ext still supported?

Re: [pyblosxom-users] 1.5 comment_draft_ext?

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

I use it, so, yes.  Why do you ask?  Are you encountering problems with it?


On 09/28/2010 10:42 AM, Joseph Reagle wrote:
> 
> Is comment_draft_ext still supported?
> 

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

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

So there were two (three) problems.

The first is that I needed to edit the .htaccess file so that I could
rewrite all the urls to a single page that redirects to the new site.

The second is that I needed to create the page that redirects.

(The third problem is that SF drives me crazy because every time I want
to go do something, I have to learn how they've changed how to do it.
Rrrr....)

The second item is/was easy.  The problem is that I didn't have
permissions to the .htaccess file and SF keeps changing how project web
directories get edited.

I talked with someone on #sourceforge to get permissions fixed and
he/she was puzzled and then told me how to get shell access which it
turned out they completely changed since the last time I fiddled with
things.

Long story short, the entire site should redirect to the new one now.
If anyone sees pages that don't, let me know.

/will


On 09/28/2010 09:58 AM, Blake Winton wrote:
>   I don't know if you can change anything on the page, but if you have 
> access to the head element, you could add
> 
> <meta  http-equiv="refresh"  content="0;url=http://pyblosxom.bluesock.org/"  />
> 
> (from <http://en.wikipedia.org/wiki/Meta_refresh#Examples>) and it 
> should do the trick.
> 
> Later,
> Blake.
> 
> On 09/28/2010 09:48 AM, will kahn-greene wrote:
>> I think I left the sites the way they were because I didn't have
>> permissions to edit certain files.  The one I want to edit is the
>> .htaccess file.
>>
>> I'll see what I can do.
>>
>>> Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect
>>> to http://pyblosxom.bluesock.org/ to avoid confusion?
>>>
> 
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
> 

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

[Blake W. <bw...@la...>]

  I don't know if you can change anything on the page, but if you have 
access to the head element, you could add

<meta  http-equiv="refresh"  content="0;url=http://pyblosxom.bluesock.org/"  />

(from <http://en.wikipedia.org/wiki/Meta_refresh#Examples>) and it 
should do the trick.

Later,
Blake.

On 09/28/2010 09:48 AM, will kahn-greene wrote:
> I think I left the sites the way they were because I didn't have
> permissions to edit certain files.  The one I want to edit is the
> .htaccess file.
>
> I'll see what I can do.
>
>> Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect
>> to http://pyblosxom.bluesock.org/ to avoid confusion?
>>

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

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

On Sep 28, 2010 at 12:39 AM +0100, seanh wrote:
> I'm just trying to get pyblosxom running so that I can make a blog on my
> desktop and preview it with paste. I'll worry about deploying it to a
> web server later. I'm going to give up for now and come back to it
> another day.

I'll be honest with you, maybe because I'm not familiar with paste, but 
installing it remotely on Ubuntu 10.04 for a 'production' server was *way* 
easier for me than trying to get it up and running under paste on OS X 
locally for hacking.  I ended up figuring I could hack in most of what I 
wanted via plugins, which was mostly true.  Though it prevents me from 
contributing back in any meaningful manner.  Someday I'll try again.

For the server, I just used easy_install:

sudo easy_install pyblosxom
pyblosxom-cmd create blog
cp pyblosxom.cgi /path/to/my/cgi/
chmod 755 pyblosxom.cgi

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

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

On Sep 28, 2010 at 09:50 AM -0400, Asheesh Laroia wrote:
> Even then, one giant GUYS THE SITE HAS MOVED notice would be way better
> than this confusing situation of two sites with content.

Unfortunately the Sourceforge site is the first couple hits on Google.  Not 
much you can do about that.  Other than to use a redirect...

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

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

On Tue, 28 Sep 2010, will kahn-greene wrote:

> I think I left the sites the way they were because I didn't have 
> permissions to edit certain files.  The one I want to edit is the 
> .htaccess file.

Even then, one giant GUYS THE SITE HAS MOVED notice would be way better 
than this confusing situation of two sites with content.

If you want, I can write you a PHP file that will cause the redirect to 
happen, BTW. If SF.net can do PHP.

-- Asheesh.

-- 
Q:	What do you call the money you pay to the government when
 	you ride into the country on the back of an elephant?
A:	A howdah duty.

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

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

I think I left the sites the way they were because I didn't have
permissions to edit certain files.  The one I want to edit is the
.htaccess file.

I'll see what I can do.


On 09/28/2010 09:04 AM, Asheesh Laroia wrote:
> On Tue, 28 Sep 2010, 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.
>>
>> 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/ ?
> 
> Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect 
> to http://pyblosxom.bluesock.org/ to avoid confusion?
> 
> -- Asheesh.

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

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

On Tue, 28 Sep 2010, 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.
>
> 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/ ?

Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect 
to http://pyblosxom.bluesock.org/ to avoid confusion?

-- Asheesh.

[pyblosxom-users] Markdown plugin rewritten as cb_story

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

New version of the Python Markdown 2 plugin:

http://github.com/seanh/PyBlosxom-Python-Markdown-2-Plugin/blob/master/markdown-plugin.py

I've only tested this very briefly. The plugin contained quite a lot of
cruft, and I wanted to cut it down to the bare minimum. It was an entry
parser plugin, I rewrote it as a preformatter, then as a postformatter,
and finally as a cb_story which seems to be the best callback for this.
It means that the markdown plugin doesn't have to worry about parsing
the entry files as an entry parser would have to and can leave that to
pyblosxom (or some entry parser plugin), but the markdown plugin can
still be selective and only apply to entries with certain filename
extensions (preformatters and postformatters can't do this). The code is
much shorter now.

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

[Will Kahn-G. <wi...@bl...>]

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.

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/ ?

2. Python/Ruby/Perl have their own packaging system which is different 
than the Ubuntu/Fedora/OpenSUSE/etc packaging systems.  There are people 
who build packages of Python/Ruby/Perl modules.

If you prefer to use your system's packaging system, then you'll have to 
either build the PyBlosxom package yourself or you'll have to wait for 
some other contributor to build it for you.

Last time I checked Tollef was maintaining the PyBlosxom package for 
Debian and I think that's the package that Ubuntu has as well.  You should 
create a Debian/Ubuntu bug to get him to update it.

3. There are a couple of different ways to install PyBlosxom because there 
are two different packaging systems for Python.  Yes, it's kind of a pain 
in the ass.  There are a lot of really great Python devs working on the 
situation currently and figuring out better solutions.

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 don't see any evidence of you being in a virtual environment in your 
emails, but I can only guess at what you did.  It's possible the 
instructions need some more work, but they're pretty basic, so I'm not 
sure what we could improve.

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.

6. You used easy_install _AND_ pip.  You don't want to mix and match 
easy_install/setuptools and pip/distribute because they don't play well 
with each other's metadata.  I'll try to make that clearer in the 
instructions.  Honestly, I didn't expect anyone to try both.


I'm sorry that it's so frustrating.

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.

/will


On Tue, 28 Sep 2010, seanh wrote:

> On Tue, Sep 28, 2010 at 12:49:53AM +0100, seanh wrote:
>>     $ cd pyblosxom-1.5rc2
>>     $ bin/pyblosxom-cmd create ./myblog
>>     ...
>>     $ cd myblog
>>     $ sudo aptitude install python-pastescript
>>     $ paster serve blog.ini
>>     Starting server in PID 2675.
>>     serving on 0.0.0.0:5000 view at http://127.0.0.1:5000
>>
>> That is, _if_ I understand things correctly and the paster server is
>> running pyblosxom from the source code files in the extracted tarball,
>> and not finding it elsewhere on my system as a result of all those
>> failed install commands. I don't know how to get back to a clean system
>> to find that out.
>
> Ok, I had a spare laptop with Ubuntu 10.04 on it so I tried the above on
> a clean system and the paster command failed with "No module named
> Pyblosxom.pyblosxom". So the reason it's working on my desktop must be
> that one of the various different install attempts succeeded. Whichever
> one it was, it required my terminal to be restarted before things would
> work.
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> pyblosxom-users mailing list
> pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>

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

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

On Tue, Sep 28, 2010 at 12:49:53AM +0100, seanh wrote:
>     $ cd pyblosxom-1.5rc2
>     $ bin/pyblosxom-cmd create ./myblog
>     ...
>     $ cd myblog
>     $ sudo aptitude install python-pastescript
>     $ paster serve blog.ini
>     Starting server in PID 2675.
>     serving on 0.0.0.0:5000 view at http://127.0.0.1:5000
> 
> That is, _if_ I understand things correctly and the paster server is
> running pyblosxom from the source code files in the extracted tarball,
> and not finding it elsewhere on my system as a result of all those
> failed install commands. I don't know how to get back to a clean system
> to find that out.

Ok, I had a spare laptop with Ubuntu 10.04 on it so I tried the above on
a clean system and the paster command failed with "No module named
Pyblosxom.pyblosxom". So the reason it's working on my desktop must be
that one of the various different install attempts succeeded. Whichever
one it was, it required my terminal to be restarted before things would
work.

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

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

Hey, after all that, I closed my terminal emulator and opened it again
to clean up my environment and:

    $ cd pyblosxom-1.5rc2
    $ bin/pyblosxom-cmd create ./myblog
    ...
    $ cd myblog
    $ sudo aptitude install python-pastescript
    $ paster serve blog.ini
    Starting server in PID 2675.
    serving on 0.0.0.0:5000 view at http://127.0.0.1:5000

So if all you want to do is try pyblosxom locally, all those install
tools seem to be unnecessary? I imagine that if I wanted to hack on
pyblosxom and git cloned it instead of downloading and extracting the
tarball, then I could run pyblosxom from the source directory the same
way as well.

That is, _if_ I understand things correctly and the paster server is
running pyblosxom from the source code files in the extracted tarball,
and not finding it elsewhere on my system as a result of all those
failed install commands. I don't know how to get back to a clean system
to find that out.

On Tue, Sep 28, 2010 at 12:39:42AM +0100, seanh wrote:
> I can't get pyblosxom-1.5rc2 to work on Ubuntu 10.04. There seems to be
> many ways of installing: pip, setuptools, easy_install, virtualenv, why
> so many? And there are two sets of installation instructions, the
> INSTALL file in the download the Installing PyBlosxom section in the
> PyBlosxom 1.5 Documentation on the website. These two seem to be
> slightly different from each other.
> 
> I'm just trying to get pyblosxom running so that I can make a blog on my
> desktop and preview it with paste. I'll worry about deploying it to a
> web server later. I'm going to give up for now and come back to it
> another day.
> 
>     $ cd ~/src/pyblosxom-1.5rc2
>     $ sudo pip install pyblosxom
>     Downloading/unpacking pyblosxom
>       Running setup.py egg_info for package pyblosxom
>         Using setuptools....
>         warning: no files found matching '*' under directory 'docs/source'
>     Installing collected packages: pyblosxom
>       Running setup.py install for pyblosxom
>         Using setuptools....
>         warning: no files found matching '*' under directory 'docs/source'
>         changing mode of /usr/local/bin/pyblosxom-cmd to 755
>     Successfully installed pyblosxom
>     
>     $ pyblosxom-cmd -v
>     Traceback (most recent call last):
>       File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
>         from Pyblosxom.commandline import command_line_handler
>     ImportError: No module named Pyblosxom.commandline
> 
>     $ sudo easy_install pyblosxom
>     Searching for pyblosxom
>     Best match: pyblosxom 1.5rc2
>     Adding pyblosxom 1.5rc2 to easy-install.pth file
>     
>     Using /usr/local/lib/python2.6/dist-packages
>     Processing dependencies for pyblosxom
>     Finished processing dependencies for pyblosxom
> 
>     $ pyblosxom-cmd -v
>     Traceback (most recent call last):
>       File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
>         from Pyblosxom.commandline import command_line_handler
>     ImportError: No module named Pyblosxom.commandline
> 
>     $ sudo python setup.py install
>     ... (lots of output)
>     $ pyblosxom-cmd -v
>     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 "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 461, in run_script
>        self.require(requires)[0].run_script(script_name, ns)
>      File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1188, in run_script
>        raise ResolutionError("No script named %r" % script_name)
>     pkg_resources.ResolutionError: No script named 'pyblosxom-cmd'
> 
> I also tried the two different sets of instructions for installing with
> virtualenv, and neither worked.
> 
> I'm stumped! And I have no idea how to clean up my system after all
> those botched install commands seem to have left a terrible mess behind.
> 
> Now I tried just cd'ing into the pyblosxom-1.5rc2 source directory and
> running `bin/pyblosxom-cmd create ./blog` and that worked, but then
> `paster serve blog.ini` fails with "ImportError: No module named
> Pyblosxom.pyblosxom". I'm not sure whether this is because previous
> install commands have made a mess of my system.
> 
> <rant>
> I hate all these language-specific package managers for Python, Ruby,
> Haskell, etc. They're a disaster. There's millions of them, they always
> fail, and they can't uninstall! So if you have a failed pyblosxom
> install or an install of an old version and you want to try out a new
> version, what can you do? You can't uninstall the old one so that you
> can be sure you're starting fresh with the new one. You just have to
> install the old version over the new one and hope for the best.
> </rant>

-- 
seanh <sn...@gm...>

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

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

I can't get pyblosxom-1.5rc2 to work on Ubuntu 10.04. There seems to be
many ways of installing: pip, setuptools, easy_install, virtualenv, why
so many? And there are two sets of installation instructions, the
INSTALL file in the download the Installing PyBlosxom section in the
PyBlosxom 1.5 Documentation on the website. These two seem to be
slightly different from each other.

I'm just trying to get pyblosxom running so that I can make a blog on my
desktop and preview it with paste. I'll worry about deploying it to a
web server later. I'm going to give up for now and come back to it
another day.

    $ cd ~/src/pyblosxom-1.5rc2
    $ sudo pip install pyblosxom
    Downloading/unpacking pyblosxom
      Running setup.py egg_info for package pyblosxom
        Using setuptools....
        warning: no files found matching '*' under directory 'docs/source'
    Installing collected packages: pyblosxom
      Running setup.py install for pyblosxom
        Using setuptools....
        warning: no files found matching '*' under directory 'docs/source'
        changing mode of /usr/local/bin/pyblosxom-cmd to 755
    Successfully installed pyblosxom
    
    $ pyblosxom-cmd -v
    Traceback (most recent call last):
      File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
        from Pyblosxom.commandline import command_line_handler
    ImportError: No module named Pyblosxom.commandline

    $ sudo easy_install pyblosxom
    Searching for pyblosxom
    Best match: pyblosxom 1.5rc2
    Adding pyblosxom 1.5rc2 to easy-install.pth file
    
    Using /usr/local/lib/python2.6/dist-packages
    Processing dependencies for pyblosxom
    Finished processing dependencies for pyblosxom

    $ pyblosxom-cmd -v
    Traceback (most recent call last):
      File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
        from Pyblosxom.commandline import command_line_handler
    ImportError: No module named Pyblosxom.commandline

    $ sudo python setup.py install
    ... (lots of output)
    $ pyblosxom-cmd -v
    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 "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 461, in run_script
       self.require(requires)[0].run_script(script_name, ns)
     File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1188, in run_script
       raise ResolutionError("No script named %r" % script_name)
    pkg_resources.ResolutionError: No script named 'pyblosxom-cmd'

I also tried the two different sets of instructions for installing with
virtualenv, and neither worked.

I'm stumped! And I have no idea how to clean up my system after all
those botched install commands seem to have left a terrible mess behind.

Now I tried just cd'ing into the pyblosxom-1.5rc2 source directory and
running `bin/pyblosxom-cmd create ./blog` and that worked, but then
`paster serve blog.ini` fails with "ImportError: No module named
Pyblosxom.pyblosxom". I'm not sure whether this is because previous
install commands have made a mess of my system.

<rant>
I hate all these language-specific package managers for Python, Ruby,
Haskell, etc. They're a disaster. There's millions of them, they always
fail, and they can't uninstall! So if you have a failed pyblosxom
install or an install of an old version and you want to try out a new
version, what can you do? You can't uninstall the old one so that you
can be sure you're starting fresh with the new one. You just have to
install the old version over the new one and hope for the best.
</rant>

Re: [pyblosxom-users] tags.py problem

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

On Aug 29, 2010 at 09:49 AM -0400, will kahn-greene wrote:
> The "A server error occurred.  Please contact the administrator." is the
> error message coming from your web-server.  There should be an error for
> the web-server.  Looking in that log will give you a better idea of what
> the problem is.

Doh, didn't think of that.  It was a long error message which ended with a 
KeyError.  Regardless, the updated tags.py fixed it.  When I diffed the new 
and old tags.py, there was only a one line difference - changing an 
AttributeError to KeyError.  All is good.

> Alternatively, the pyblosxom.cgi file has a line like this towards the
> top of the file:
>
>    #import cgitb; cgitb.enable()
>
> This is somewhat covered in the Trouble-Shooting section:

I think I had tried this, but the traceback might be getting masked since 
I'm running nginx as a reverse proxy to apache.  Since the problem is fixed, 
I won't invest too much time into getting cgitb working right - I'll just 
check the error logs if need be.

Thanks!

pyblosxom is pretty cool.  I realize I've more or less built up simple 
home-built version of it for just generating a static site.  I think I'll be 
moving that site over to pyblosxom completely and then look into writing 
some plugins, etc.

Re: [pyblosxom-users] tags.py problem

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

Hi Tim!

The "A server error occurred.  Please contact the administrator." is the
error message coming from your web-server.  There should be an error for
the web-server.  Looking in that log will give you a better idea of what
the problem is.

Alternatively, the pyblosxom.cgi file has a line like this towards the
top of the file:

    #import cgitb; cgitb.enable()

If you remove the # from the beginning of that line, then the traceback
will show up in your browser rather than the vague error message from
your web-server.  The traceback will make it easier to ascertain what
the problem is.

This is somewhat covered in the Trouble-Shooting section:

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

Having said all that, Mako just sent in a patch to tags.py.  You might
be hitting the problem he hit.

So before you start trouble-shooting, it might be good to grab the
latest tags.py plugin:


http://gitorious.org/pyblosxom/pyblosxom/blobs/raw/master/plugins/tags/tags.py

That file has Mako's fix.

If that doesn't fix your issue, you'll have to trouble-shoot the
problem.  If you need help, don't hesitate to ask.

/will


On 08/28/2010 01:40 PM, Tim Gray wrote:
> I've just started playing around with pyblosxom and it looks pretty nice. 
> I'm having an issue with the tags plugin though.  When I run 'pyblosxom-cmd 
> buildtags', a tags file is made specified location.  It appears to have 
> picked up the correct data too.  Furthermore, when I check my website in 
> debug mode, the Request.get_data() dict has an entry 'tagsdata' that has the 
> right information.  This goes away if I disable the plugin.
> 
> The problem is when I enable the tags plugin and turn off debug mode, I get 
> the following message:
> "A server error occurred.  Please contact the administrator."
> 
> When I disable the tags plugin, the site works fine.
> 
> This is on 1.5rc2 with the tags.py that came with the distribution.
> 
> Any ideas?

[pyblosxom-users] tags.py problem

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

I've just started playing around with pyblosxom and it looks pretty nice. 
I'm having an issue with the tags plugin though.  When I run 'pyblosxom-cmd 
buildtags', a tags file is made specified location.  It appears to have 
picked up the correct data too.  Furthermore, when I check my website in 
debug mode, the Request.get_data() dict has an entry 'tagsdata' that has the 
right information.  This goes away if I disable the plugin.

The problem is when I enable the tags plugin and turn off debug mode, I get 
the following message:
"A server error occurred.  Please contact the administrator."

When I disable the tags plugin, the site works fine.

This is on 1.5rc2 with the tags.py that came with the distribution.

Any ideas?

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

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

On 08/09/2010 04:43 PM, Hauke Fath wrote:
> At 11:05 Uhr -0400 3.8.2010, will kahn-greene wrote:
>> I just release pyblosxom 1.5rc2.  It consists mostly of fixes to
>> plugins, additional tests, and documentation updates.
> 
> I am the maintainer of the pkgsrc py-blosxom package
> <http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/py-blosxom/README.html>. A
> few minor pleas from here:
> 
> Please be consistent in naming the releases (*1.5-rc1 vs. *1.5rc2), and the
> tarball (pyblosxom-*.tgz vs. pybloxsom*.tgz). pkgsrc can work around quirks
> like that, but they makes updating the package lengthier than needs be.

I changed version naming to be valid per the Python version metadata spec:

    http://www.python.org/dev/peps/pep-0386/

This allows versions to be compared correctly when using PyPI and other
tools.  If you check the Pyblosxom/pyblosxom.py file, you'll note that
I've codified the new version scheme that will be used going forward.


> The masters of pkgsrc like to know what's different in an update, so it
> would be helpful if there were release-specific (or at least dated)
> sections in the changelog.

I don't plan on doing this for rc releases.  rc releases are not
considered final and are considered to be unstable.  For now, if you
want to see what's changed, grab the repository and look at "git log".

If someone wants to volunteer to take the notes in git log and convert
them into an appropriate changelog for rc releases, that'd be super,
too.  Just let me know and I'll point you in the right place and we'll
figure out what the workflow should look like.

/will

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

[Hauke F. <ha...@Es...>]

At 11:05 Uhr -0400 3.8.2010, will kahn-greene wrote:
>I just release pyblosxom 1.5rc2.  It consists mostly of fixes to
>plugins, additional tests, and documentation updates.

Thanks, Will!

I am the maintainer of the pkgsrc py-blosxom package
<http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/py-blosxom/README.html>. A
few minor pleas from here:

Please be consistent in naming the releases (*1.5-rc1 vs. *1.5rc2), and the
tarball (pyblosxom-*.tgz vs. pybloxsom*.tgz). pkgsrc can work around quirks
like that, but they makes updating the package lengthier than needs be.

The masters of pkgsrc like to know what's different in an update, so it
would be helpful if there were release-specific (or at least dated)
sections in the changelog.

Keep up the good work!

	hauke

--
"It's never straight up and down"     (DEVO)

Re: [pyblosxom-users] [installation] pip install pyblosxom failed

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

I released PyBlosxom 1.5 rc2 last week and also updated PyPI.  So "pip
install pyblosxom" works now.

Additionally, I tweaked the PyBlosxom web-site, so doing "pip install -f
http://pyblosxom/bluesock.org/ pyblosxom" also works now.

I forgot to add download_url to the metadata in setup.py.  I'll do that
in the next release.  After doing that, PyPI will pick it up and other
versions of "pip install" should work better.

Thank you for pointing this out!

/will


On 07/25/2010 10:17 AM, Frédéric Hébert wrote:
> Hello,
> 
>  (my apologies I've subscribed for the digest form of the list and then
> could not retrieve the thread and then could not answer to it in the
> right place)
> 
> Pip works in a very similar way of easy_install, by listing and caching
> links from Pypi indexes and honours options like '--find-links',
> '--index-url' and so on. It seems that pip could not retrieve archives
> from sourceforge links. I made a test with PyFFI package of which Pypi
> index offers only sourceforge download links.
> It failed also (see http://pastebin.com/iagLGjje).
> 
> On the contrary, easy_install can install (pyblosxom) from sourceforge
> links. easy_install pyblosxom works !
> 
> In regards to the download page of bluesock.org, AFAICS pip honours a
> default level of recursion (maybe 2 ??) and then don't reach the
> download page.
> 
> Anyway, IMHO the best way to get rid of these "limitations" (?) is to
> add a link to http://pyblosxom.bluesock.org/download/ from pyblosxom 's
> pypi index.
> (see the result of 'pip install -f
> http://pyblosxom.bluesock.org/download/ -U --log log.txt pyblosxom' at
> http://pastebin.com/NXmJV0Tv).
> 
> Frédéric

[pyblosxom-users] pyblosxom 1.5rc2 released!

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

Hi!

I just release pyblosxom 1.5rc2.  It consists mostly of fixes to
plugins, additional tests, and documentation updates.

I also updated PyPI so doing::

    pip install pyblosxom

works now.

Additionally, I tweaked the web-site so it's easier to find the most
recent release and older releases in the sidebar.

Plus I wrote up the release process because I had to go figure it out again.

Things I could use some help with:

1. reviewing, correcting and updating documentation

2. updating plugins in the contributed plugins pack to work with
PyBlosxom 1.5, adding tests for them, and cleaning up the plugin code

3. adding tests for PyBlosxom

4. making the web-site prettier, more useful, and less "busy"

5. writing a plugin that makes the front page static rather than an
index of blog entries

I could really use your help.  If you're interested in helping, but
don't know where to start, let me know.  I hang out as willkg on
#pyblosxom on freenode.

Rock on!

/will