This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients iritkatriel, oliphaunt, sumagnadas, terry.reedy, trrhodes
Date 2021-09-24.20:14:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632514481.18.0.757493851894.issue41914@roundup.psfhosted.org>
In-reply-to
Content
Léon's message from #45242, which I closed as a duplicate of this.

Leon: please try with 3.11 (best, repository main), 3.10, or at least 3.9.  3.8 and before only get security fixes.
---

Building Python 3.7, I ran into the same issue reported [here] (only line numbers differ):

======================================================================
FAIL: test_errors_in_command (__main__.PdbTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "Lib/test/test_pdb.py", line 1535, in test_errors_in_command
    '(Pdb) ',
AssertionError: Lists differ: ['(Pd[283 chars]efined", 'LEAVING RECURSIVE DEBUGGER', '(Pdb) ', '\x1b[?1034h'] != ['(Pd[283 chars]efined", 'LEAVING RECURSIVE DEBUGGER', '(Pdb) ']

First list contains 1 additional elements.
First extra element 9:
'\x1b[?1034h'

  ['(Pdb) *** SyntaxError: unexpected EOF while parsing',
   '(Pdb) ENTERING RECURSIVE DEBUGGER',
   '*** SyntaxError: unexpected EOF while parsing',
   'LEAVING RECURSIVE DEBUGGER',
   '(Pdb) ENTERING RECURSIVE DEBUGGER',
   '> <string>(1)<module>()',
   "((Pdb)) *** NameError: name 'doesnotexist' is not defined",
   'LEAVING RECURSIVE DEBUGGER',
-  '(Pdb) ',
?          ^

+  '(Pdb) ']
?          ^

-  '\x1b[?1034h']

----------------------------------------------------------------------
Ran 39 tests in 1.024s

FAILED (failures=1)


I have also managed to determine the cause.  As can be seen, the output from this pdb invocation contains an extraneous ANSI control sequence ("interpret "meta" key, set eighth bit"). This happens when running the test inside the GNU `screen` environment.  Run the test outside `screen`, and the problem goes away.

(By the way, this was the only test that failed when running `make test` inside the `screen` environment.)
History
Date User Action Args
2021-09-24 20:14:41terry.reedysetrecipients: + terry.reedy, trrhodes, iritkatriel, sumagnadas, oliphaunt
2021-09-24 20:14:41terry.reedysetmessageid: <1632514481.18.0.757493851894.issue41914@roundup.psfhosted.org>
2021-09-24 20:14:41terry.reedylinkissue41914 messages
2021-09-24 20:14:41terry.reedycreate