New submission from Tarek Ziadé <ziade.ta...@gmail.com>: test_subprocess.test_executable now has a failure in the subprocess created (see http://www.python.org/dev/buildbot/builders/amd64%20gentoo%20trunk/builds/303/steps/test/logs/stdio)
the bbots don't get red because this is happening in the subprocess and the test just look for the return code. This is hapenning since I've added the sysconfig module. This change revealed a bug in subprocess. This call : subprocess.Popen(["somethingyoudonthave", "-c", "import sys; print sys.executable"], executable=sys.executable) will print a directory name for sys.executable, instead of the real value. That's fooling sysconfig, which is now called through site.py, to set a few variables. ---------- assignee: jnoller components: Library (Lib) messages: 98257 nosy: jnoller, tarek priority: normal severity: normal status: open title: subprocess executable option wrong location type: behavior versions: Python 2.7, Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7774> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
