Ole, Is this the PyPI package? https://pypi.python.org/pypi/vpp-papi
If it is, how often will the package be updated? Also, it would be helpful to include in release notes VPP versions supported. Thanks Feng On Mon, Oct 9, 2017 at 5:09 AM, Ole Troan <otr...@employees.org> wrote: > Alec, > > > A good step in the right direction. How does this translate in terms of > python package versioning? > > Ideally, we should have a python PyPI package for programming VPP using > python library. > > Currently, it does not at all translate to python package versioning. > There is already a PyPI package. > > The VPP Python binding is currently completely independent of VPP version. > I might have taken the fact that it is a dynamic language a bit too far, > but currently on connect, combined with the JSON definitions the Python > binding dynamically creates the API. Of course given the flexibility of > plugins and that plugins provider their own APIs, tightly coupling VPP > Python binding and VPP version is a little tricky. > > I was thinking of adding a more application friendly wrapper for dealing > with API module versions. Something like pass in a associative array of > modules + required versions, and get a yes/no reply back. > > Best regards, > Ole > > > > > > From: <vpp-dev-boun...@lists.fd.io> on behalf of "Marek Gradzki -X > (mgradzki - PANTHEON TECHNOLOGIES at Cisco)" <mgrad...@cisco.com> > > Date: Thursday, October 5, 2017 at 4:38 AM > > To: Ole Troan <otr...@employees.org>, vpp-dev <vpp-dev@lists.fd.io> > > Subject: Re: [vpp-dev] API versioning > > > > +1 > > > > having explicit version number in the api file is a good thing in my > opinion. > > > > I think also Java bindings could benefit a bit from your proposal. > > > > While the only backward compatible api change is probably parameter > rename, > > one could generate more human friendly error messages on CRC mismatch. > > > > Regards, > > Marek > > > > -----Original Message----- > > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] > On Behalf Of Ole Troan > > Sent: 2 października 2017 14:37 > > To: vpp-dev <vpp-dev@lists.fd.io> > > Subject: [vpp-dev] API versioning > > > > All, > > > > I have received a few suggestions that especially the dynamic language > bindings (Python, Lua) would benefit from a better versioning system than > depending and storing the CRC values of each VPP API message. > > > > Could you please take a look at the proposal for semantic versioning of > API modules here: > > https://wiki.fd.io/view/VPP/API_Versioning > > > > Dave helped me with modifying the .api parser: > > https://gerrit.fd.io/r/#/c/8589/ > > > > This patch adds a new message "api_versions". That will return a > dictionary of API modules and their versions. > > > > I have also added version 1.0.0 to all .api files. Please let me know if > you want a different version string. E.g. major == 0, if it is experimental > and expected to change. > > > > Opinions? > > (and yes, I know we can do better with additional support for backwards > compatibility... one baby step at the time. ;-)) > > > > Best regards, > > Ole > > _______________________________________________ > > vpp-dev mailing list > > vpp-dev@lists.fd.io > > https://lists.fd.io/mailman/listinfo/vpp-dev > > > > > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
