Ned Deily <[email protected]> added the comment:
Re-opening. The new test_cmd_line_script fails on macOS framework builds
because the test case assumes that the file name in sys.executable will appear
in the error message. For macOS framework builds, sys.executable is the file
name of the stub launcher and its file name bears no relationship to the file
name of the actual python executable:
$ python3.7 -c 'import sys;print(sys.executable)'
/usr/local/bin/python3.7
$ python3.7 -m test test_cmd_line_script
Run tests sequentially
0:00:00 load avg: 1.12 [1/1] test_cmd_line_script
test test_cmd_line_script failed -- Traceback (most recent call last):
File
"/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/test/test_cmd_line_script.py",
line 648, in test_nonexisting_script
self.assertIn(program, err)
AssertionError: 'python3.7' not found in
"/Library/Frameworks/Python.framework/Versions/3.7/Resources/Python.app/Contents/MacOS/Python:
can't open file 'nonexistingscript.py': [Errno 2] No such file or directory\n"
test_cmd_line_script failed
For now, I'm going to disable the test for macOS frameworks but the test should
get fixed.
----------
nosy: +ned.deily
resolution: fixed ->
stage: resolved -> patch review
status: closed -> open
versions: +Python 3.8
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue34783>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
