You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion, "need", as in "is it a requirement", is a pretty strong statement. No, we don't need LXML. I was able to get python-cybox working (as far as I could tell; all tests passed) with xml.etree without too many changes, with Python 2. (And python-stix and python-maec too.) Python 3 didn't work only because with that version, the etree classes are no longer pure-Python, and I couldn't mark them up with extra attributes.
The core of my strategy for converting from LXML to xml.etree was to add extra attributes to the element nodes, to mimic the extra namespace info LXML adds. That way, all the code would still work, which expected those attributes to be there. And this is why it failed under Python 3. I think it's still possible to make it work, but it would require more extensive changes.
Perhaps the reason LXML is used is because generateDS generates code which uses that package. When generateDS was brought in, LXML came along for the ride and has been there ever since. But I don't know for sure.
Activity
chisholm commentedon Nov 5, 2015
In my opinion, "need", as in "is it a requirement", is a pretty strong statement. No, we don't need LXML. I was able to get python-cybox working (as far as I could tell; all tests passed) with xml.etree without too many changes, with Python 2. (And python-stix and python-maec too.) Python 3 didn't work only because with that version, the etree classes are no longer pure-Python, and I couldn't mark them up with extra attributes.
The core of my strategy for converting from LXML to xml.etree was to add extra attributes to the element nodes, to mimic the extra namespace info LXML adds. That way, all the code would still work, which expected those attributes to be there. And this is why it failed under Python 3. I think it's still possible to make it work, but it would require more extensive changes.
Perhaps the reason LXML is used is because generateDS generates code which uses that package. When generateDS was brought in, LXML came along for the ride and has been there ever since. But I don't know for sure.