Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #103412 > unrolled thread

Re: nosepipe error

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: nosepipe error Dan Stromberg <drsalists@gmail.com> - 2016-02-23 10:11 -0800

#103412 — Re: nosepipe error

On Tue, Feb 23, 2016 at 9:43 AM, Chris Angelico <rosuav@gmail.com> wrote:
> On Wed, Feb 24, 2016 at 4:36 AM, Dan Stromberg <drsalists@gmail.com> wrote:
>> Message: Unhandled exception in thread started by
>> sys.excepthook is missing
>> lost sys.stderr
>>
>> That 1433299041 looks like ASCII:
>>>>> hex(1433299041)
>> '0x556e6861'
>>>>> chr(0x55) + chr(0x6e) + chr(0x68) + chr(0x61)
>> 'Unha'
>>
>> ...but I'm not sure where to go with that from there.
>
> My eye sees those characters as being the beginning of "Unhandled
> exception in thread". You could be dealing with multiple levels of
> cascading exceptions.

Agreed - at least "Unhandled exception".

I'm seeing, in the nosepipe code:
        # we use stdout for IPC, so block all other output
        self._stream = sys.__stdout__

I'm not sure using stdout/stdin for IPC is a great thing; a lot of
tests write to stdout or stderr, whether intentionally or
unintentionally.

I'm attempting to replace the use of stdout/stdin with os.pipe(), but
so far I'm not having much luck.  I get three write()'s, and then a
hang.  So far, I'm ignoring the fact that os.read() and os.write()
might split or aggregate chunks over a socket, since this is a
socketpair communicating on the same machine.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web