This one couldn’t be simpler, but it’s worth noting all the same. I’ve just
experienced a situation where a virtualenv was being completely ignored by
all tools even though it was absolutely activated via source bin/activate.
The answer was to blow away the lib directory within the virtualenv and
blow away the local Python interpreter at bin/python and re-create the
virtualenv. After deactivating and re-activating, everything works correctly again.
I guess something in the environment (or env variables) got messed up.
Who knows; it works now.
It’s amazing to see how technologies can be so smoothly integrated these
days. I’m talking, at least in this instance, about how setuptools
works with PyPI (and then Plone.org’s Products section) and allows you
to distribute your product(s) to the world. So far, I’ve just got the
one — collective.portlet.googleapps — but I’m sure time will pass and
I’ll have some more useful things to contribute. Here’s a summary of
what I did:
Create the product. ZopeSkel is a wonderful help here for Plone
products. [I lie a little bit in …
EDIT: Watch out for python-ldap 2.3.10, the latest version at time
of writing. Seems like there’s an issue with it and Centos 5.4. Forcing
python-ldap to be version 2.3.8 works, though. (easy_install python-ldap==2.3.8)
Previously, you might have read about setting up a Virtualenv on Ubuntu
Jaunty. Now, that was reasonably painless since python-virtualenv and
python-setuptools is in the Ubuntu repo. Whether it’s my Centos servers
and their misguided repos or me just not being able to find such a
related rpm packages, Centos just needs little more love to get …
Two blog entries in one day - wow it’s been a good work day.
Just a quick chronicle of my thoughts: version conflicts in buildout
aren’t always pretty. My latest escapade into trying to load up Varnish
through zc.buildout resulted in a hair-tearing out message:
An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 1477, in main
File "/tmp/tmp8o-_PD/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py …