-
Notifications
You must be signed in to change notification settings - Fork 21
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
namespace missing in exception messages for XML documents #77
Comments
In case there's any question, this is still an open issue. My project has a unit test that accommodates the unexpected exception message. I'll know this issue is fixed when that unit test starts failing... |
I don't know if this is the same issue, but I can feed this into from_raw:
and it is happy, but it fails if I feed the equivalent into from_xml:
It fails with a namespace missing exception on class, which is an identyRef,. I can send you [email protected], though it won't accept it here. (It is publicly available on the internet) |
In addition, on any system running netopeer2, if you do a netconf get with a subtree filter of either of these two:
or
then the form_xml on the result will always fail. |
[This is happening in my fork. I haven't tested against yangson/master yet]
The path provided in an error message from SchemaNode.from_raw() with an input document that has an unexpected leaf node:
The path provided in an error message from SchemaNode.from_xml() with an input document that has an unexpected leaf node:
The XML code should provide the namespaces in the same way. This may be related to the more general issue about how the XML code is inconsistent with how namespaces are represented in the
ET
structures: sometimes the namespace is in theattrib
and sometime it's mangled into thetag
.The text was updated successfully, but these errors were encountered: