[Smtk-developers] Python wrapping

[TJ Corona]

> I fear the bindings are getting stale in places where API has been added

I totally agree. The original plan was to bootstrap our bindings with the scripts and then tend to them by hand. We may be able to put together something runs the generator script and diffs it with the files in the code base. That way, we would only need to keep around a list of the custom-omitted methods. Either way, it is definitely true that maintenance plans for pybind bindings have been neglected to date.

What does everyone else think?

Thomas J. Corona, Ph.D.
Kitware, Inc.
Senior R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4443

> On Sep 15, 2017, at 9:09 AM, David Thompson <david.thompson at kitware.com> wrote:
> 
>> ... This MR adds an example for passing multiple include paths to the python script. I’d be happy to make the interface less clunky if you think that would help (you are not the first person who found this syntax unintuitive).
> 
> Thanks, TJ. The example helps. In the longer term, it would be nice to work out what include paths are passed to the compiler for a given module so it is easier to run this.
> 
> I fear the bindings are getting stale in places where API has been added since they were first generated because the process is mysterious to us ignoramuses and because it can be hard to reconcile manual changes to the generated code if you weren't the one who made the manual changes to begin with.
> 
> 	David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/smtk-developers/attachments/20170915/da5efa04/attachment.html>