On 10/06/2017 09:15 AM, Josef Reidinger wrote: > V Thu, 5 Oct 2017 10:56:05 -0600 > David Mulder <[email protected]> napsáno: > >> Since the python bindings were very broken, and being deprecated... >> >> https://github.com/dmulder/yast-python-bindings2 >> >> I wrote new python bindings. They still need some work, but they're >> able to run my yast python modules now. >> The crash at shutdown is gone, and I now get extensive debug when >> something goes wrong. Much better! >> These bindings are generated using SWIG, plus there's some wrapper >> functions to simplify things on the python side. >> >> Suggestions? Feedback? > > Hi, few notes: > > 1. whole UI related stuff should be done using common import + UI.call > as it is already attached to component system and it is not written in > ruby. > > 2. yast.py is basically reimplementation of yast stuff in python. I am > not sure if it is right way, as anything you will need you have to > reimplement > > 3. your modules is not possible to call from rest of YaST. For ycp, > perl and ruby it is possible to call it from each other.
Well, to be fair, most of the recent Ruby code is written to be consumed only by Ruby. It has been quite some time since we stopped caring about providing a YCP interface for everything we do. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
