Binary garbage in /etc/lsb-release (on Travis CI) #15

While implementing a fix for #10 I found a really weird edge case that (so far) has only manifested in the Python 2.6 environment on Travis CI: The parsing of /etc/lsb-release results in the expected variable names but the values contain binary garbage including nul bytes. Here's a failing Travis CI build where the following log message can be observed (hard wrapped for readability):

Extracted 4 variables from /etc/lsb-release:
{u'DISTRIB_CODENAME': 't\x00\x00\x00r\x00\x00\x00u\x00\x00\x00s\x00\x00\x00t\x00\x00\x00y\x00\x00\x00',
 u'DISTRIB_RELEASE': '1\x00\x00\x004\x00\x00\x00.\x00\x00\x000\x00\x00\x004\x00\x00\x00',
 u'DISTRIB_ID': 'U\x00\x00\x00b\x00\x00\x00u\x00\x00\x00n\x00\x00\x00t\x00\x00\x00u\x00\x00\x00',
 u'DISTRIB_DESCRIPTION': '\x00\x00\x00U\x00\x00\x00b\x00\x00\x00u\x00\x00\x00n\x00\x00\x00t\x00\x00\x00u\x00\x00\x00 \x00\x00\x001\x00\x00\x004\x00\x00\x00.\x00\x00\x000\x00\x00\x004\x00\x00\x00.\x00\x00\x005\x00\x00\x00 \x00\x00\x00L\x00\x00\x00T\x00\x00\x00S\x00\x00\x00\x00\x00\x00'}

At first this seemed a minor annoyance in the sense that the test suite failed on this and that needed a workaround (see d3451a9). However since then I found that this also has an adverse effect on the test suite of another project of mine which uses executor.

This has left me wondering whether this weird edge case is isolated to the Python 2.6 environment on Travis CI or whether this is a symptom of a bigger problem, possibly a programming error on my side. The weird thing is that the Python 2.7, 3.4, 3.5, 3.6 and PyPy builds all work fine...

In the short term I'm worried that I may have broken the distributor_id and distribution_codename logic for more environments then just the Python 2.6 environment on Travis CI, so I'm going to add a "countermeasure" of sorts to executor.