Exception when non-ASCII character appears in invalid ANSI escape sequence

[pexpect]

Exception when non-ASCII character appears in invalid ANSI escape sequence

[jquast]

.. yes, these things, including pexpect/init.py should just use the logging module, and then any consumer could set their own logging preferences (and log formatters). Unfortunately we have a bit of a 10-year legacy to maintain (I can only imagine what kind of weird pipelines pexpect logfiles may find themselves in),

The logfile should be opened in an encoding, like utf8 or cp437 in your case. We can fix that with your related unicode bugs. It could also use the %r or '{!r}'.format functions, so it would write to the ascii file as '\u2562' instead of trying to write ╢. That would probably be the easiest short-term fix if you're pressing for one --
fout.write ("%r, %r\n" % (fsm.input_symbol, fsm.current_state,))

[dcoshea]

The reference to this issue in the above commit/pull request #96 was incorrect. I do have a fix for this issue that I plan to submit a pull request for once issue #84 is fixed.

[jquast]

Closing, pexpect's terminal emulation code remains next release but no longer improved, marked deprecated by #240 Suggest any terminal emulation / screen scraping code efforts moved to more concerted project efforts such as https://github.com/selectel/pyte