Re: pyblosxom 1.5rc2 released!

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 <[email protected]>

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