Message 114971 - Python tracker

this affects 2.7 as well. the problem was introduced by r78136 which skips out of the directory containing newly built libpython2.7, so the linking command cannot find it in -L. and fails (unless a systemwide libpython is already present)

the tests should probably specify that they want to link to a specific file, instead of relying on -lpython
however, i have no idea how to do that in general, let alone within distutils :/

see also issue8335