[Python-Dev] Help needed: problems getting the expected default encoding for embedded IO config test
Nick Coghlan
ncoghlan at gmail.com
Thu Oct 17 18:25:26 CEST 2013
http://bugs.python.org/issue16129 added a Py_SetStandardStreamEncoding
API to allow embedding applications like Blender to explicitly
configure the encoding and error handler for the standard IO streams.
However, the test case didn't get along with the buildbots, and I'm
struggling to figure out why.
To deal with the possible variation in the default encoding across
systems, I use sys.std*.encoding to work out the expected default
encoding for the streams.
However, as you can see in an example like
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.0%203.x/builds/579/steps/test/logs/stdio,
this is failing, with the encoding in the *expected* data being None,
while the values from the subprocess actually look right. In the
"re-run at the end" case, it all works fine, so it doesn't appear to
be anything inherently wrong with the affected systems.
The test pass without any problems on my own system (otherwise I
wouldn't have checked it in). Running the full test suite the same way
the buildbots do also worked fine locally.
I've marked the offending test as skipped for now (and reopened the
tracker issue), and will look into it more tomorrow. but figured I'd
mention it here in case anyone had any good suggestions (the next
thing on my to try list is running with the hash seed from one of the
failing buildbots, in case it's a cross-test interference problem).
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
More information about the Python-Dev
mailing list