diff options
author | Chris St. Pierre <chris.a.st.pierre@gmail.com> | 2013-11-21 13:03:04 -0500 |
---|---|---|
committer | Chris St. Pierre <chris.a.st.pierre@gmail.com> | 2013-11-21 13:06:36 -0500 |
commit | 0f8d403d1a86cfbfe8222662dc445e16e8f7eff9 (patch) | |
tree | 1d88be64858b41fc8a8f7dace060649b6ed9127c /osx/Introduction.txt | |
parent | f4dc3f33579584924243ac2e89f6f68ed195ec79 (diff) | |
download | bcfg2-0f8d403d1a86cfbfe8222662dc445e16e8f7eff9.tar.gz bcfg2-0f8d403d1a86cfbfe8222662dc445e16e8f7eff9.tar.bz2 bcfg2-0f8d403d1a86cfbfe8222662dc445e16e8f7eff9.zip |
Bundler: Fix parsing XML template output with encoding declaration
lxml 3.2.1 complains when you try to parse a unicode (in Python 2) or
string (in Python 3) containing an XML document with an encoding
declaration. Traceback:
ValueError: Unicode strings with encoding declaration are not
supported. Please use bytes input or XML fragments without
declaration.
This encodes the document as a string (in Python 2) or bytes (in
Python 3) to avoid the lxml error. There may be other places this
happens, too, although in most other cases we should use
lxml.etree.parse() to parse a file, or we parse strings (in Python 2)
instead of unicode objects.
Diffstat (limited to 'osx/Introduction.txt')
0 files changed, 0 insertions, 0 deletions