I was hoping to add a detached_display (or similarly named) module that makes your hack a little cleaner. This kind of thing would be really good for debugging.
Alternatively we could just add a parameter to the raw_display.Screen.__init__ that tells it to go use some other pty. Having some URWID_ environment variables that override things like which pty to use, what encoding to expect, how many colours to use is another thing that could be really useful (but possibly dangerous) On Wed, Sep 10, 2014 at 10:06 AM, Maxim Lacrima <[email protected]> wrote: > Okay, I was able to get it working to some extent. > > I just opened another terminal, and hardcoded `urwid.raw_display.Screen`: > > self._term_output_file = open('/dev/pts/8', 'wb', 0) > self._term_input_file = open('/dev/pts/8', 'rb', 0) > > Now I can see urwid output on a different terminal, while debugging on > another. This very ugly hack, so is there a better way? > > > On 10 September 2014 16:28, Maxim Lacrima <[email protected]> wrote: >> >> Hello! >> >> How would I run urwid app under pdb? If I run: >> >> python -m pdb examples/tour.py >> >> then the screen becomes cluttered because urwid writes to stdout and pdb >> writes to stdout as well. The same problem is with stdin. >> >> Thanks. >> >> -- >> Regards, >> Maxim > > > > > -- > Regards, > Maxim > > _______________________________________________ > Urwid mailing list > [email protected] > http://lists.excess.org/mailman/listinfo/urwid > _______________________________________________ Urwid mailing list [email protected] http://lists.excess.org/mailman/listinfo/urwid
