Had this issue when you’ve been trying to run something like
Funnelweb, and you hit an ImportError for BeautifulSoup? You’re
definitely not alone, because I just hit the same issue. The answer is
simple — just ensure that you don’t use BeautifulSoup 4 or above (this
is still beta) — it uses a different namespace, specifically bs4.
Thus, whilst you might have the BeautifulSoup egg satisfying your
dependencies, any imports of this package are going to fail.
For me, I’m using buildout, so I just pinned my version of BeautifulSoup thusly:
This is pretty trivial (and trivial to fix), but I’m chronicling it for
my knowledge as much as anyone else’s. The issue is that a given Python
egg is missing some form of files, most commonly the ‘docs’ directory in
my experience, because the build wasn’t configured correctly.
The error goes somewhat like this:
Getting distribution for 'my.theme'.
error: docs/HISTORY.txt: No such file or directory
An error occured when trying to install my.theme 1.5.0. Look above this message for any errors that were output by easy_install.
Update: You should check out wildcard.fixpersistentutilities
- it’s a fantastic solution to problems like this. Many thanks to
Nathan Van Gheem, the author of the add on. Check out the link and
see how to install it (temporarily) on your Plone instance that
needs its site manager cleaned up.
Leftovers are typically useful when they’re in your fridge at home. They
mean you don’t have to mess around making lunch for the next day for
work, and can just grab them, and walk right out the door. Now,
leftovers in the zope.component SiteManager aren’t …
Here’s an interesting error message I got stumped with for a good set of
hours. The issue started with me using collective.autoreload with Plone
and it does the trick, mostly. With any such ‘operation’ and live
reloading of code for Python, you’ve got to expect that not everything
will go according to plan. Most things do, but one issue I found
presented with this error message:
< ... huge traceback ...>
TypeError: super(type, obj): obj must be an instance or subtype of type
The issue arises for me (and you’ll probably see it elsewhere) when I go
Welcome to the new year! It’s the start of another journey around the
sun and the beginning of work for me. Whilst I’m the only one actually
working around here today, I thought I’d take the chance and update with
some useful info:
Troublesome Python eggs
Now, much to my amazement, when you’re creating/compiling/whatever
Python eggs for Plone you need to actually specify the files you want
included in the build. I suppose it’s fair enough, but thought it might
have actually done it for me. No such luck!