On Apr 5, 2009, at 11:36 AM, Nick Rothwell wrote:
> On 4 Apr 2009, at 19:35, Philip Jenvey wrote:
>> sys.stdout = os.fdopen(sys.stdout.fileno(), sys.stdout.mode, 0) # 0
>> means unbuffered
> OK... I've modded my embedded wrapper for Jython so that the
> interpreter has a stdout which I post-process myself - this works
> fine. Perhaps understandably, I still don't get Python compilation
> errors appearing when I do the same for stderr - I guess these are
> coming straight from Java.
What errors exactly? I just closed this ticket out the other day:
For that bug I verified that exception information does in fact go to
our stderr. You can do what I was doing (shown in the bug) to verify
if the message is going through Jython's stdout/err.
> The incantation above (with stderr instead of stdout) doesn't seem to
> have any effect.
Jython's stderr isn't buffered.