Adapt CFFI bindings for libyang v5 (soversion 5.0.0+)#169
Conversation
cc425f7 to
1aa6dfb
Compare
April 2, 2026 10:04
|
thanks, I'm also interested in v5! can someone review the changes? @rjarry @choppsv1 @jeremie6wind @samuel-gauthier |
Sorry, something went wrong.
|
Ping? Anyone here, any help needed? |
Sorry, something went wrong.
|
the activity is low in this repo, so i guess it will take some time until someone responds |
Sorry, something went wrong.
|
Sorry for the delay, we will have a look before the end of May. Thanks for your work, much appreciated. |
Sorry, something went wrong.
Adapt CFFI bindings for libyang v5 (soversion 5.0.0+) Update cdefs.h, source.c, and Python call sites to match the libyang 4.2.2 -> 5.0.0 API changes: - parent field type changed from lyd_node_inner* to lyd_node* across all node structs - lyd_any_value_str gained a LYD_FORMAT parameter - lys_find_child signature was reworked - lyd_node_any lost the union lyd_any_value/LYD_ANYDATA_VALUETYPE fields - LYD_NEW_VAL_BIN / LYS_GETNEXT_WITHSCHEMAMOUNT removed tests: fix failures caused by libyang v5 changes Add missing ietf-inet-types YANG module to the test search path, as libyang v5 no longer resolves it automatically. Update the module data callback test to handle the ietf-inet-types dependency, and adjust expected error paths to match libyang v5 output. Signed-off-by: Antonio Prcela <antonio.prcela@gmail.com>
|
done thanks for the update on when it will be reviewed |
Sorry, something went wrong.
|
Hello @precla , |
Sorry, something went wrong.
49a1e9a
into
CESNET:master
May 18, 2026
Update cdefs.h, source.c and Python call sites to match the libyang 4.2.2 -> 5.0.0 API changes:
lyd_node_inner*tolyd_node*across all node structslyd_any_value_strgained aLYD_FORMATparameterlys_find_childsignature was reworkedlyd_node_anylost the unionlyd_any_value/LYD_ANYDATA_VALUETYPEfieldsLYD_NEW_VAL_BINandLYS_GETNEXT_WITHSCHEMAMOUNTwhich are not exiting anymore in libyang