![](https://secure.gravatar.com/avatar/3e7e975f0fa432f4ae6604f72c132309.jpg?s=120&d=mm&r=g)
On Sun, May 11, 2008 at 1:48 PM, Mike Meyer <mwm@mired.org> wrote:
On Sun, 11 May 2008 09:01:01 +0200 Stefan Behnel <stefan_ml@behnel.de> wrote:
you ask why this is so hard? Simple answer: because no-one has contributed a way so far to make it easier.
Gee, I had no trouble at all doing this last week (the release of Oracle library bits for Intel OS-X means it's now desirable). I installed macports, did a self-update, then installed py25-lxml. It installed python2.5.2 and the versions of libxml2 and libxslt that were in macports as part of the process.
The build of lxml doesn't fail and you probably won't see any errors unless you are using xpath. In fact, running selftest.py after building passes for me (I'm not sure if that runs all tests or not) but I do get a consistent segfault in my program. Looking at the macport of py25-lxml I don't see any flags that would indicate they have accomplished statically linking the new libxml libs. I don't like to use ports of python modules because /opt/local/bin/python doesn't mix well with a Framework python installation from my experience.