| 1 |
On 01/28/2013 12:20 PM, Fabian Groffen wrote: |
| 2 |
> On 28-01-2013 11:41:53 -0800, Zac Medico wrote: |
| 3 |
>>> interestingly enough, this problem occurs exactly at the moment that |
| 4 |
>>> PipeLogger._start() is invoked and self.stdout_fd is None |
| 5 |
>> |
| 6 |
>> You could try removing these FD_CLOEXEC lines from PipeLogger, which are |
| 7 |
>> relatively new, to see if that helps: |
| 8 |
> |
| 9 |
> Thanks, I've removed that piece, looked like it worked, but eventually |
| 10 |
> it broke down the same way. |
| 11 |
|
| 12 |
You might try adding Darwin to the _disable_openpty list in |
| 13 |
pym/portage/util/_pty.py, to see if the pty device is what's triggering it. |
| 14 |
-- |
| 15 |
Thanks, |
| 16 |
Zac |
Archives