Python bindings by default

[Quentin Stafford-Fraser]

John Ralls <jralls at ceridwen.us> writes:
> 
> For Macs, the reason is that each version of OSX provides a different version of Python*, and the python bindings C library has to link against libpython. So python would have to be included in the bundle, which is already over 100M thanks to having to ship a separate WebKit (one that integrates with Gtk). Worse, any python script that accesses the bindings would have to run the bundled python, not any of the ones provided by the OS.

> 


On 2 Mar 2012, at 16:39, Derek Atkins wrote:
> 
> And for Windows we would have to provide Python.
> 

Mmm.  Yes, good points.  So I guess what we really need is an easy way for people with Python to build a module that links to their GnuCash installation, rather than having to rebuild GnuCash or ship Python.  

I guess that would involve something like including headers in the distribution to give prototypes for library functions, and then having a separate module that could be built using the standard Python setuptools stuff, once given the location of the installation.

Q