Python bindings

I just landed the first part of the python bindings. I still need to
finish wrapping about 50 functions by hand (anything involving varargs,
GLists and the like requires hand wrapping), but the basics are there.

I have not turned them on in the build yet, since they are not really
useful in their current state. However, the configure script does check
for the relevant stuff already (it's harmless that they are not used).
If you are really desperate to experiment (or help), just add 'python'
to the SUBDIRS variable in libmrproject/Makefile.am and then run
autogen.sh again.

Richard, Mikael: there is an implicit dependency on PyGTK for building
this stuff. I will set it up so that things will quietly fail (just not
build the bindings) if PyGTK is not installed, but do you think it is
too onerous to require this to make the bindings build work? The reason
for the requirement is that PyGTK installs the pygtk-codegen script for
generating most of the function wrappers.

An alternative to this dependency is that I can check in the generated
file (mrproject.c) and update it from time to time, but that seems
inelegant.

Any advice on this issue appreciated.

Cheers,
Malcolm

-- 
Tolkien is hobbit-forming.