Comment 3 for bug 614522

Well, that's an underscore prefixed function that was never intended to be publicly exposed, so I feel little guilt about breaking bzr-xmloutput. It's easy to resolve in the short term, just change the import to `from (xml.etree|elementtree).ElementTree import _escape_cdata` instead (with try/except ImportError obviously). The functions at the top of bzrlib.xml8 would also be an option, but I'd prefer if it moved instead to something public and documented.

Looking at the bzr-xmloutput code, the way it is currently creating xml is... not nice, and bug 568941 seems to show it has big problems anyway.