Re: assertXMLEqual behaviour

2014-04-30 Thread James Bennett
As far as I can tell from reading the source, there's no deliberate intention one way or another. However, from a strict/pedantic point of view, the example you give is demonstrating correct behavior; due to whitespace, the second document contains nodes not present in the first one. -- You rece

assertXMLEqual behaviour

2014-04-30 Thread Jon Dunleavy
Hi, I am using django 1.6 but I can't find any information on the bugtracker as to whether this has changed but is this intentional behaviour of assertXMLEqual: # this passes self.assertXMLEqual( "Value", """Value""", ) # this fails self.assertXMLEqual( "Value", """ Val