[lxml-dev] Binary egg for Mac OS X

Martin Aspeli optilude+lists at gmail.com
Sat Jun 27 15:40:19 CEST 2009


Martin Aspeli wrote:

> Erm... seems I spoke too soon. I thought it was working, but somehow my 
> setuptools is building a lxml-2.2.1-py2.4-macosx-10.3-i386.egg in 
> preference over lxml-2.2.1-py2.4-macosx-10.5-i386.egg, even though I'm 
> on OSX 10.5.

Okay. So it seems there were two problems.

1) Buildout tried to build an lxml 10.3 egg instead of using the binary 
one. That was a local issue. I fixed it like this:

  - Upgrade MacPorts' python to 2.4.6 (possibly unnecessary)
  - Re-run boostrap.py in the buildout
  - Remove the lxml egg from my eggs cache
  - Remove the lxml tgz download from the dist directory of my download 
cache
  - Re-running buildout

2) The egg now installs, but it appears to be broken. The problem is 
that the egg is somehow 'nested'. In my eggs cache, I have:

$ ls lxml-2.2.1-py2.4-macosx-10.5-i386.egg/
lxml-2.2.1-py2.4-macosx-10.5-i386.egg/

$ ls 
lxml-2.2.1-py2.4-macosx-10.5-i386.egg/lxml-2.2.1-py2.4-macosx-10.5-i386.eggEGG-INFO/ 
lxml/

If I fix the egg manually, it works fine.

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book



More information about the lxml-dev mailing list