Closed exquo closed 4 months ago
Can reproduce with urwid v2.6.x
. No problem on v2.5.3
or earlier.
I don't know, when this was added, but the watch_pipe function of the main_loop follows this schema:
watch_pipe(callback: Callable[[bytes], bool]) → int
If the callback function doesn't return True, it seems to be assumed false and the read end of the pipe gets closed. That's why you can see the first line being logged as normal, but nothing after that.
@MareOfNights thanks for the quick and insightful troubleshooting!
Here is the breaking commit: https://github.com/urwid/urwid/commit/1a5b18ca0b34876d6aa4937efca28751748d0f23#diff-350a967d4905ac920fdbd363bd511deffdfc3f52fe7920a384ad67ee8a13dd9b
I've asked about this upstream: https://github.com/urwid/urwid/issues/847. Let's see if they consider this a regression.
Originally posted by @0x09AF in https://github.com/isamert/scli/issues/220#issuecomment-1964398743