Re: Problems with pyarchives

will guaraldi <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.user
Message-ID <[email protected]>
Just for some backstory here, I know for a fact that the version of
pyarchives that is kicking up the error you're getting is not the one that
comes with 0.8.1 since prior to the changes I did a couple of weeks ago
there were no calls to tools.Walk where the first argument is the Request
object.  Thus the error you're getting is coming from the version of
pyarchives that's in CVS still.

Re-installing PyBlosxom won't change anything since none of the plugins
are installed in the base installation.  The pyarchives.py file that you
want will be in contrib/plugins from the tar.gz file.

The version line of the file you want is something like:

__version__ = "$Id: pyarchives.py,v 1.12 2003/08/28 06:52:06 wari Exp $"


I guess to fix this, I would check the following things:

1. verify that there aren't any other versions of pyarchives.py floating
around

2. make sure the version of pyarchives in your plugin dirs have the above
version line.  if they don't, they're the wrong version.

3. make sure you're copying pyarchives.py from the ./contrib/plugins
directory from the tar.gz file into your plugin dir and not the version
that the registry errantly points to.


See if that helps.

/will


On Sun, 29 Feb 2004, Wolfgang Stief wrote:
>
> Hello Will!
>
> Thanks for your initial hints.
>
> ...
>
> I checked several times: removed the site-python/Pyblosxom/* of my
> Python installation, reinstalled pyblosxom-0.8.1 ('python ./setup.py
> install'), copied pyarchives.py to my plugin directory, changed
> config.py.
>
> Result: Same error as before:


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.