-
Notifications
You must be signed in to change notification settings - Fork 52
data: option to allow json int/bool as strings #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
ca54ed6
to
b829165
Compare
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
b829165
to
c249839
Compare
CESNET/libyang#2344 has now been merged, just forced a rebuild of this to show tests pass. |
I guess it must be pulling from master instead of devel when building C libyang .... so still failing |
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
@rjarry can you review, approve, and merge? |
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
CESNET/libyang-python#134 needed for backwards compatibility for existing configurations.
@rjarry @samuel-gauthier any chance one of you can review? |
Is the feature available in a public release of libyang? If so, please change the minimum required version here: Line 9 in 3072af0
Otherwise we need to wait for a release. |
Yes, available as of the official 3.12.2 release. I'll update this PR with that, but the other PR I have open I can't really update that to without conflict. Both depend on the same 3.12.2 however (technically, it was introduced in the 3.7 series but no official release was made for those). |
a212ca0
to
c127f99
Compare
cffi/source.c
Outdated
#if (LY_PROJ_VERSION_MAJOR != 3 || LY_PROJ_VERSION_MINOR < 12) | ||
#error "This version of libyang bindings only works with libyang 3.12+" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LY_PROJ_VERSION_* constants are only recent. Could you keep the test on LY_VERSION_* so that error messages are useful when building with ancient libyang versions?
Also, as you said, your series depends on CESNET/libyang@2d477f52d5c8 (I may be wrong about the exact SOVERSION, please do verify my claim).
Even if it wasn't an official tagged release, you can still depend on that specific version.
#if (LY_VERSION_MAJOR != 3 || LY_VERSION_MINOR < 8)
#error "This version of libyang bindings only works with libyang 3.8+"
#endif
810f744
to
e3467e6
Compare
Depends on CESNET/libyang#2344 Add support for new option to python bindings. Signed-off-by: Brad House <[email protected]>
@rjarry sorry for the delay, got busy. Fixed the version check as per your request. |
Depends on libyang 3.12.2 or higher
Add support for new option to python bindings.