Comment #6 on issue 1623 by pekka.klarck: XML library: Support using lxml
module to get better xpath support
http://code.google.com/p/robotframework/issues/detail?id=1623
Based on lxml docs about performance <http://lxml.de/performance.html> it
seems that we would not get much, if any, better performance if we switched
Robot to use lxml.etree instead of cElementTree internally. Some quotes
from the aforementioned docs:
"""For plain parser performance, lxml.etree and cElementTree tend to stay
rather close to each other, usually within a factor of two, with winners
well distributed over both sides. Similar timings can be observed for the
iterparse() function."""
"""For applications that require a high parser throughput of large files,
and that do little to no serialization, both cET and lxml.etree are a good
choice. The cET library is particularly fast for iterparse applications
that extract small amounts of data or aggregate information from large XML
data sets that do not fit into memory."""
Based on this information, and due to possible backwads incompatibility
problems, it makes no sense to switch to lxml internally. We'll obviously
add it to XML library, though.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
