[issue17756] test_syntax_error fails when run in the installed location

Ezio Melotti added the comment: I'm going to close this since the reported issue has been fixed. In the test sys.stderr was mocked, and Mock.method_calls simply records the calls done to the mock. Therefore the fact that 'NameError' and ':' were written on sys.stderr on two separate calls to

[issue17756] test_syntax_error fails when run in the installed location

Terry J. Reedy added the comment: In the absence of any further issue in over a year, can this be closed? -- nosy: +terry.reedy ___ Python tracker ___ ___

[issue17756] test_syntax_error fails when run in the installed location

Matthias Klose added the comment: not yet closing, to see if there are some stream buffering issues in mock -- ___ Python tracker ___

[issue17756] test_syntax_error fails when run in the installed location

Roundup Robot added the comment: New changeset 20db5e9086d4 by doko in branch '3.4': - Issue #17756: Fix test_code test when run from the installed location. http://hg.python.org/cpython/rev/20db5e9086d4 New changeset 8885fc2e92b3 by doko in branch 'default': Merge from 3.4: http://hg.python.org

[issue17756] test_syntax_error fails when run in the installed location

Matthias Klose added the comment: sure, doing this. my follow-up question was if it is necessary to fix anything else in unittest. -- ___ Python tracker ___

[issue17756] test_syntax_error fails when run in the installed location

Michael Foord added the comment: It looks like the simplest fix would be to change "NameError:" to "NameError", as the problem is that they're (sometimes!?) on separate lines. This still tests what we want to test. -- ___ Python tracker

[issue17756] test_syntax_error fails when run in the installed location

Matthias Klose added the comment: adding unittest developers -- nosy: +ezio.melotti, michael.foord ___ Python tracker ___ ___ Python-b

[issue17756] test_syntax_error fails when run in the installed location

Martin Pitt added the comment: I can reproduce this here. In that test, I added the following: with open('/tmp/debug', 'w') as f: for call in self.stderr.method_calls: f.write('call: %s\n' % str(call)) This gives: === 8< call: call.writ

[issue17756] test_syntax_error fails when run in the installed location

Matthias Klose added the comment: seen this again in our autopkg tester https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-python3.4/12/ however now I can't reproduce this locally, and the test succeeds during the build. -- status: pending -> open __

[issue17756] test_syntax_error fails when run in the installed location

Georg Brandl added the comment: Can't reproduce with current 3.3 tip. -- nosy: +georg.brandl resolution: -> out of date status: open -> pending ___ Python tracker ___ __

[issue17756] test_syntax_error fails when run in the installed location

New submission from Matthias Klose: no idea yet about that one ... == FAIL: test_syntax_error (test.test_code_module.TestInteractiveConsole) -- Traceback (most