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
ncclient should require minimum of lxml>=3.3.0 #84
Conversation
Fixed in 0.4.7 https://github.com/ncclient/ncclient/tree/v0.4.7 thnx for pointing it out |
Hi Brian, Some days ago, Thomas pointed out that the lxml version req could be lowered: #109. In the meantime I am trying to run your unittest locally but I fail to do so - maybe I have missed something... :
I have tested with lxml-3.2.1 , 3.3.6, 3.5.0 Thnx in advance, Best, |
Also, it would help if you could include your test in ncclient's unit tests Thnx again, Best, |
e8e04fb
to
25a8945
Compare
NOTE: Force pushed updated to this branch |
@@ -0,0 +1 @@ | |||
<?xml version="1.0" encoding="UTF-8"?><rpc xmlns:if="http://www.cisco.com/nxos:1.0:if_manager" xmlns:nfcli="http://www.cisco.com/nxos:1.0:nfcli" xmlns:nxos="http://www.cisco.com/nxos:1.0" xmlns:vlan_mgr_cli="http://www.cisco.com/nxos:1.0:vlan_mgr_cli" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:UUID-HERE"><get><filter type="subtree"><cmd>show version</cmd></filter></get></rpc> |
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.
the xmlns order changed between now, and the last time I messed with this. I'm not sure the best way to deal with this.
Should the resulting xml be parsed, and the object diff'd ?
I don't want to ignore all the attributes in the root node because that is where the problem was with lxml 3.2.1
Thoughts / ideas ?
The requirement is now |
This test is looks ugly to me, so it should probably not be merged, without a little more massaging.
The actual fix is bumping the version in requirements.txt
...
Added test that reproduces problem when using lxml<3.3.0
When sending multiple messages the state of the attributes bleeds into the next message.
This was fixed in lxml-3.3.0beta4
Originally reported: https://bugzilla.redhat.com/show_bug.cgi?id=1242011