[issue7885] test_distutils fails if Python built in separate directory

Ned Deily added the comment: It looks like this was fixed as part of the changes for Issue12141 (which were also backported to 2.7.x); test_build_ext tests are now cleanly skipped if the include file cannot be found. -- nosy: +ned.deily resolution: -> out of date stage: needs patch ->

[issue7885] test_distutils fails if Python built in separate directory

Mark Lawrence added the comment: Is this still an issue that needs addressing? I can't try it myself as I use Windows. -- nosy: +BreamoreBoy ___ Python tracker ___ _

[issue7885] test_distutils fails if Python built in separate directory

Changes by Éric Araujo : -- assignee: tarek -> eric.araujo nosy: +dmalcolm, eric.araujo versions: +Python 3.1 -Python 2.6 ___ Python tracker ___ __

[issue7885] test_distutils fails if Python built in separate directory

Dan Dever added the comment: Adding version 2.6 This fails for me with 2.6.5 in the same way. -- nosy: +dedded versions: +Python 2.6 ___ Python tracker ___ _

[issue7885] test_distutils fails if Python built in separate directory

Roumen Petrov added the comment: r78136 completely broke this build. before was enough to add "old workdir" in first place as library directory to make test_get_outputs happy -- nosy: +rpetrov ___ Python tracker _

[issue7885] test_distutils fails if Python built in separate directory

New submission from Neil Schemenauer : Lib/test/test_distutils.py crashes if Python was built in a directory other than the source directory. Using a separate build directory is handy if you are building Python with different sets of configure options since you only need one copy of the sourc