Comment 12 for bug 354205

Great,
Just had a chance to test. I removed my manual install of the Mapnik python bindings, purged and re-installed 'python-mapnik' package, ensured both python2.5 and python2.6 were installed, and then was able to successfully do:

>>> import mapnik

when running the python interpreter both with the default python26 and after jumping into a python2.5 interpreter by typing:

$/usr/bin/python2.5

Thanks so much for this fix!

The only odd thing is that both the python2.6 and python2.6 Mapnik shared object '_mapnik.so' files appear to be linked against libboost_python*py25*.so. I would assume this would cause problems (based on my experience from Mac OSX and boost libs). $ldd against the boost_python libs show they do not explicitly link against any version of python. Can someone with an understanding of library linking on linux explain why this works?

Anyway, I'm glad it does work - thanks for everyone's effort!

- Dane