Hi Paul, Picking off one issue at the time.
> Why won't Ole, as maintainer, allow it? > > The build system uses something called vppapigen to generate the c include > files and the json files. It could as easily generate static stubs so that > development with python could be usable without a running vpp instance. I certainly didn't intend for my opinion to come off as a "don't allow". Initially the Python code was fully generated from vppapigen. With a class per .api file and fully formed methods. Later it evolved to dynamically create all functions based on the API representations in JSON. (This latter change made the Python binding independent of VPP version which is how it was possible to individually package it and put it on PyPI, but lets do that on a separate thread.) Generating Python code from vppapigen is simple. But just how do you want these stubs to look like and how should they be packaged and used? If I have pushed back on this it's likely more out of ignorance of the problem rather than ill will. ;-) Best regards, Ole
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18032): https://lists.fd.io/g/vpp-dev/message/18032 Mute This Topic: https://lists.fd.io/mt/78229638/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-