GitLab

This is especially important for the JS file.

See also 1dd2faa2de16.

This is to fix SEDA exports tests on python3.

We first dump XML documents as unicode using the _encoding argument
introduced in previous changeset. Accordingly, expected files are
changed to remove the XML declaration because dumped values will not
contain them.

Then we open files in text mode (using io.open() for consistency between
python2 and python3) and do string formatting using unicode values.
(Especially, six.binary_type(<some integer>) produces different values
in python2 and python3, and we actually want to stringify the integer --
the eid value.)

This is useful in tests because the doctest comparison engine from lxml
works better with text objects. The new _encoding argument is
essentially used a "encoding" argument of lxml's etree.tostring() which
will hence serialize to a unicode string. When doing so, we must also
avoid any XML declaration (otherwise, lxml messes up when loading the
content, not sure why), so we insert the "standalone" flag only when
dumping to bytes.

We use io.open() to consistently open files in text mode in both python2
and python3 (we use text mode because we need to .format() the read
string, which is only possible with text on python3). Accordingly, we
set encoding=text_type when dumping XML to string, in order to produce a
unicode string.

Apparently, this is what python2 does.

`max(maxc, maxvalue)` would evaluate to `max("Infinity", <some
integer>)` when maxc is graph_nodes.INFINITY. While this works on
python2 (by chance, since strings and integers can be compared), this
does not on python3.

We thus move the "if" that checks for graph_nodes.INFINITY inside the
"for" loop.

In python3, lxml.etree.tostring returns bytes but we expect text in
tests. By passing six.text_type as encoding parameter to this function,
it returns a unicode string.