Re: [OpenBabel-Devel] Extending what is exported through the python interface

2013-11-15 Thread Noel O'Boyle
Oh right. If I were you I would just use a Python dictionary by Atom Id to store the info. Otherwise, I would double check first of all that the code works from C++ (the quick way of doing this is grepping our source code for any usage of OBPairFloatingData - I have a suspicion that I tried to use

Re: [OpenBabel-Devel] Extending what is exported through the python interface

2013-11-15 Thread Casper Steinmann
Hi, I know the specifics about the git-stuff - it was more a question about what can go through the SWIG interface - I am not familiar with the details at all and the openbabel-python.i file was kinda intimidating. The super class of the OBPairFloatingData is something based on templates and I tho

Re: [OpenBabel-Devel] Extending what is exported through the python interface

2013-11-15 Thread Noel O'Boyle
Fork on github, make branch called pythonpair, fix issue, send pull request. As a matter of interest, why do you need this specific functionality? - Noel On 6 November 2013 16:31, Casper Steinmann wrote: > Hi, > > I wonder what the formal approach is if I want to export > OBPairFloatingPoint to

[OpenBabel-Devel] Extending what is exported through the python interface

2013-11-15 Thread Casper Steinmann
Hi, I wonder what the formal approach is if I want to export OBPairFloatingPoint to the python interface (and the others of course). Any points would be appreciated. thanks Casper -- DreamFactory - Open Source REST &