[issue21264] test_compileall fails to build in the installed location

2015-10-09 Thread Brett Cannon
Brett Cannon added the comment: I consider this fixed by way of issue #25099. If that's wrong then feel free to open the issue again. -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> test_compileall fails when run by unprivileged user o

[issue21264] test_compileall fails to build in the installed location

2015-09-25 Thread Brett Cannon
Changes by Brett Cannon : -- assignee: -> brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue21264] test_compileall fails to build in the installed location

2015-09-25 Thread Brett Cannon
Brett Cannon added the comment: Issue #25099 seems to also be related to a similar issue. A proposed fix can be found over there. -- nosy: +brett.cannon ___ Python tracker ___ _

[issue21264] test_compileall fails to build in the installed location

2015-09-19 Thread R. David Murray
R. David Murray added the comment: Yes the point is to test compilation of the path. If I run python3 -m compilelall on my installed python, it works fine (zero return code). I can't really investigate this further right now, but it isn't obvious to me what the answer is from the information

[issue21264] test_compileall fails to build in the installed location

2015-09-18 Thread Terry J. Reedy
Terry J. Reedy added the comment: David, I am nosying you because this issue proposes to modify two test functions you added to test_compileall. See my prior message. -- For me, the test failed at every first occurrence of 'PYTHONPATH=' in the 3 functions. With one occurrence removed, the next

[issue21264] test_compileall fails to build in the installed location

2015-09-18 Thread Terry J. Reedy
Terry J. Reedy added the comment: Verified failure on installed 3.4.3, Win 7, with 3 rather than 1 error (all similar). test_no_args_compiles_path (test.test_compileall.CommandLineTests) ... FAIL test_no_args_respects_force_flag (test.test_compileall.CommandLineTests) ... FAIL test_no_args_resp

[issue21264] test_compileall fails to build in the installed location

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

[issue21264] test_compileall fails to build in the installed location

2014-05-06 Thread Matthias Klose
Matthias Klose added the comment: what happens here: PYTHONPATH=$(pwd) python3.4 -X faulthandler -S -m compileall Skipping current directory Listing '/home/packages/python/3.4/x'... Compiling '/home/packages/python/3.4/x/foo.py'... Listing '/usr/lib/python3.4/'... Listing '/usr/lib/python3.4/pla

[issue21264] test_compileall fails to build in the installed location

2014-04-16 Thread Matthias Klose
New submission from Matthias Klose: the installation directory is non-writable, and the byte code files don't exist. [1/1] test_compileall test test_compileall failed -- Traceback (most recent call last): File "/usr/lib/python3.4/test/test_compileall.py", line 194, in test_no_args_respects_fo