Issue1266

PythonInterpreter does not have anymore setOut(StringWriter) and
setOut(StringWriter), so it's not backward compatible anymore (and a lot
of coding based on previous Jython versions  is broken).

This was removed by pjenvey in r3682, see the log comment "kill
PythonInterpreter.setOut/Err(Writer) and the associated Writer backed
  PyFile support"

Phil may have more insight into why we chose to have this backwards
incompatibility, part of an overall change to rewrite PyFile to use NIO.

Thanks. For me, the strength of java  is in backward compatibility.
There is no point in introducing new features in v2.5 
if we did not stick to this concept for jython.
For me, I would rather use v2.2 if there is no way around
using PythonInterpreter in its original form.

I personally would prefer if PythonInterpreter remains completely
backwards compatible. Given that java.io.OutputStreamWriter, along with
an encoding (perhaps default), can be used to bridge to byte streams,
this would seem feasible to support #setOut and #setErr.

Fixed by r6103. Sergei, please test to verify this works for you.

Thanks, I've checked, the  dev version looks fine now.

cheers,

Closing due to user verification and new unit test.