lxml on OSX -- solved

Hi guys. I've been investigating building lxml on OSX for quite some time now.

Here's the scoop so far:

• I want to use buildout
  
• I want NOT to use Apple's libraries (libxml, libxslt)
  
• On OSX there's no "--rpath" option available, thus there's no way to tell an executable on link time where to look for dynamic libraries
  
• This is disgusting (do we have 2008 or what?)

Ok, that's what I've come up with. Note the z3c.recipe.egg, it allows for arguments to the setup script, which the original zc.recipe.egg does not. The version 2.0.6 of lxml has a fix for OSX in, which allows to do away with DYLD_LIBRARY_PATH, BUT you need a DYLD_FORCE_FLAT_NAMESPACE=1. Don't ask. I have no idea.

[lxml]
parts=
libxml2
libxslt
lxml-download
lxml-build

[libxml2]
recipe = zc.recipe.cmmi
url = http://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/libxml2-2.6.26.tar.gz
extra_options = --without-python

[libxslt]
recipe = zc.recipe.cmmi
url = http://ftp.gnome.org/pub/GNOME/sources/libxslt/1.1/libxslt-1.1.16.tar.bz2
extra_options = --with-libxml-prefix=${buildout:directory}/parts/libxml2/
            --without-python

[lxml-download]
recipe = plone.recipe.distros
urls = http://codespeak.net/lxml/lxml-2.0.6.tgz
version-suffix-packages = lxml-2.0.6.tgz

[lxml-build]
recipe = z3c.recipe.egg:setup
setup = ${lxml-download:location}/lxml
args =
clean
build
bdist_egg
--with-xslt-config=${buildout:directory}/parts/libxslt/bin/xslt-config
develop = true

You use it like:

[buildout]
extends=
   lxml.cfg
parts=
   ${lxml:parts}
eggs=
   ${lxml:eggs}

Ahhhh, new post at last.

Wohoo. A new post.

Finally we sorted out some issues at my company, where I'm partner.

And I got more into Python and Plone. I visited some Plone sprints:

• the Toerggelen Sprint
• The Snow Sprint 2007
• The Sorrento Sprint 2007

I'll try to attend some more, like the sprint in Potsdam later this year.

Oh, yes, the Plone Conference and Sprint? I'll be there! 

Google's GData API

I'm currently investigating the use of the GData API when it comes to create a command line blog posting tool written in pure python.

Well, it seems that there's no Python API for the pure Google Data stuff yet (I know about the Google Base Data API).

But from what I've understood this is all pure HTML POST and GET using an extended version of the ATOM XML schema. Using urllib and ElementTree in python its just plain simple to actually get your blog feeds. They've even built in some sort of query language.

Unfortunately, to authenticate with Google using your Google account, there's a bit more involved. The Java guys have it better here: There's a nice high-level API. Doh.

Authentication is, as far as I understood, needed to post blog entries.

Note to myself:

• Investigate Google Authentication wrt. Plone PAS
• provide a pure python script which posts to a blog
• hook script into a plone work flow to publish atricles from plone to blogs. Create a new content type for that, track blog post IDs we got back from google inside plone. Use Five and notifiers to update blog if Plone document changes. This would be a PIS module.