[PATCH] Python bindings (with much of the core api)
Derek Atkins
warlord at MIT.EDU
Mon Mar 24 10:29:43 EDT 2008
Hi,
Mark Jenkins <mark at parit.ca> writes:
> Hello again,
>
> I submitted a patch with the beginning of python binding support on
> February 27. ([PATCH]: Python bindings)
>
> Since then, Jeff Green and I have begun adding support for the core api,
> much of which is now accessible with the python bindings provided by the
> attached patch. See
> src/optional/python-bindings/example_scripts/simple_test.py
> (file in the patch)
> for an example where two accounts are added as children of the root
> account, and a transaction created.
>
> I've tested this against trunk, revision 17040.
Quick question: Is there any reason you're duplicating the swig
wrapping from existing .i files? Can you not use the same interface
files for guile and python?
> I know this probably isn't right, but after applying the patch to trunk
> you have to re-run autogen.sh (if you're working with a local copy where
> it has already been run), to get ./py-compile installed into the source
> directory.
Yes, this is correct. You need to re-run autogen when you add a new
directory to the tree. Another thing to note is that when you add a
new optional directory you also need to add it to DIST_SUBDIRS
otherwise "make dist" (or distcheck) will fail if you configured the
to-be-disted tree without your optional directory enabled.
DIST_SUBDIRS completely overrides SUBDIRS so if you have DIST_SUBDIRS
then you need to include all the subdirs in it (optional or
otherwise).
> Can we start a branch derived from trunk to bring these python bindings
> up to maturity?
Sure. But do you really need a branch, rather than working in trunk?
Do you really expect that you'll be breaking the existing code while
you work on the bindings?
> Mark
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord at MIT.EDU PGP key available
More information about the gnucash-devel
mailing list