[issue22895] test failure introduced by the fix for issue #22462

Roundup Robot added the comment: New changeset e4b986350feb by Antoine Pitrou in branch '3.4': Close issue #22895: fix test failure introduced by the fix for issue #22462. https://hg.python.org/cpython/rev/e4b986350feb New changeset 4990157343c6 by Antoine Pitrou in branch 'default': Close issue

[issue22895] test failure introduced by the fix for issue #22462

Antoine Pitrou added the comment: This should be fixed now. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue22895] test failure introduced by the fix for issue #22462

Antoine Pitrou added the comment: > What about using “not sysconfig.is_python_build()”? I had forgotten about it, thank you. -- ___ Python tracker ___ __

[issue22895] test failure introduced by the fix for issue #22462

Éric Araujo added the comment: What about using “not sysconfig.is_python_build()”? -- nosy: +eric.araujo ___ Python tracker ___ ___ Py

[issue22895] test failure introduced by the fix for issue #22462

Antoine Pitrou added the comment: > do we have something like skipIfInstalled? No. There's no exact way of checking for an installed Python, but one possibility is to test whether a given directory exists (e.g. "Modules"). -- ___ Python tracker

[issue22895] test failure introduced by the fix for issue #22462

Matthias Klose added the comment: do we have something like skipIfInstalled? -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue22895] test failure introduced by the fix for issue #22462

Antoine Pitrou added the comment: Thanks. So, this is not a regression: the failing test was introduced in #22462 and probably would have not worked before, either. The problem is that "../Modules/pyexpat.c" makes sense from the checkout directory but not necessarily from the install location.