On 2013-05-31, at 20:43 , Andrew Barnert wrote:That seems rife with potential issues and unintended side-effects e.g.
> try:
> from lxml import etree as ET
> except ImportError:
> from xml.etree import ElementTree as ET
>
> Your registration mechanism would mean they don't have to do this; they just import from the stdlib, and if lxml is present and registered, it would be loaded instead.
while lxml does for the most part provide ET's API, it also extends it
and I do not know if it can run ET's testsuite. It also doesn't handle
ET's implementation details for obvious reasons.