Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-09-04 Thread c . holtermann
Am 2018-07-10 20:58, schrieb David Osguthorpe: Hi All, In upgrading to gnucash 3.2 from 2.6.18 and updating my python scripts I have found an issue with the gnucash bindings and python 3. I saw this with query runs that failed to produce any results when they should have, and used to under

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-09-04 Thread c . holtermann
Hello all, I just realized (because John showed me) that this bug report: https://bugs.gnucash.org/show_bug.cgi?id=796137 and this mail thread are related. regards, Christoph Am 2018-07-19 15:42, schrieb Derek Atkins: John Ralls writes: Funny... 15+ years ago it WAS an Enum, but changed

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-19 Thread Derek Atkins
John Ralls writes: >> Funny... 15+ years ago it WAS an Enum, but changed to a string because >> we wanted to enable searching on plug-in modules. > > OK, and enums are immune to run-time changes implied by a plugin > module, but there are better ways than strings to tag types. Glib > provides

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-16 Thread John Ralls
> On Jul 16, 2018, at 10:09 AM, Derek Atkins wrote: > > John Ralls writes: > >>> When it moves to C++ you can just use std::string. :) >> >> An enum would be safer, faster, smaller, more intuitive, and wouldn’t >> break swig. > > Funny... 15+ years ago it WAS an Enum, but changed to a

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-16 Thread Derek Atkins
John Ralls writes: >> When it moves to C++ you can just use std::string. :) > > An enum would be safer, faster, smaller, more intuitive, and wouldn’t > break swig. Funny... 15+ years ago it WAS an Enum, but changed to a string because we wanted to enable searching on plug-in modules. >

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-12 Thread John Ralls
> On Jul 12, 2018, at 7:23 AM, Derek Atkins wrote: > > John Ralls writes: > >>> PS. Another solution would be to force byte string only arguments for >>> python 3 using a SWIG define SWIG_PYTHON_STRICT_BYTE_CHAR. >>> >>> This would require a major re-write of the gnucash_core.py to perform

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-12 Thread Derek Atkins
John Ralls writes: >> PS. Another solution would be to force byte string only arguments for >> python 3 using a SWIG define SWIG_PYTHON_STRICT_BYTE_CHAR. >> >> This would require a major re-write of the gnucash_core.py to perform the >> unicode<->byte transformations. > > ISTM it would be

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-10 Thread David Osguthorpe
OK Will file a bug - plus file a fix for GSList which is still needed. David On Tue, Jul 10, 2018 at 10:28 PM, John Ralls wrote: > > > > On Jul 10, 2018, at 11:58 AM, David Osguthorpe < > david.osgutho...@gmail.com> wrote: > > > > Hi All, > > > > > > In upgrading to gnucash 3.2 from 2.6.18

Re: [GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-10 Thread John Ralls
> On Jul 10, 2018, at 11:58 AM, David Osguthorpe > wrote: > > Hi All, > > > In upgrading to gnucash 3.2 from 2.6.18 and updating my python scripts I > have found an issue with the gnucash bindings and python 3. > > > I saw this with query runs that failed to produce any results when they

[GNC-dev] Problems with python 3 and the gnucash python bindings.

2018-07-10 Thread David Osguthorpe
Hi All, In upgrading to gnucash 3.2 from 2.6.18 and updating my python scripts I have found an issue with the gnucash bindings and python 3. I saw this with query runs that failed to produce any results when they should have, and used to under 2.6.18. So far it appears the issue is with the