From: Dmitry T. <dty...@gm...> - 2010-11-02 16:14:23
|
> Which means when using > cElementTree, we need both cElementTree.Comment and > ElementTree.Comment available. Crazy! :-) > Personally, I consider this a bug in cElementTree (it works with the > builtin serializers because cElementTree actually uses ElementTree's > serializers and they test again ElementTree.Comment) as it makes it > ridiculously difficult to test for comment nodes in our own code when > we are supporting both ElementTree and cElementTree at the same time. I agree with you. It "defeats the purpose of cElementTree in the first place". > However, given the current rate of ElementTree's development right > now, I would expect that a fix would take a long time to propagate to > all our users, so I've just committed what should be a working > workaround. Thanks, now I can remove my workarounds. > Please let me know if you run into any problems with it. No problems discovered. |