From 0aa2b90fc0a9975221ae8f8e94df61bb788877bc Mon Sep 17 00:00:00 2001 From: Jiri Denemark Date: Fri, 11 Mar 2011 13:44:20 +0100 Subject: python: Use hardcoded python path in libvirt.py This partially reverts (and fixes that part in a different way) commit e4384459c93e3e786aa483c7f077d1d22148f689, which replaced ``/usr/bin/python'' with ``/usr/bin/env python'' in all examples or scripts used during build to generate other files. However, python bindings module is compiled and linked against a specific python discovered or explicitly provided in configure phase. Thus libvirt.py, which is generated and installed into the system, should use the same python binary for which the module has been built. The hunk in Makefile.am replaces $(srcdir) with $(PYTHON), which might seem wrong but it is not. generator.py didn't use any of its command line arguments so passing $(srcdir) to it was redundant. --- libvirt-override.py | 5 ----- 1 file changed, 5 deletions(-) (limited to 'libvirt-override.py') diff --git a/libvirt-override.py b/libvirt-override.py index 909ebe3..d544a0e 100644 --- a/libvirt-override.py +++ b/libvirt-override.py @@ -2,11 +2,6 @@ # Manually written part of python bindings for libvirt # -# Specify -i commandline option after python was started -if __name__ == "__main__": - import os - os.environ["PYTHONINSPECT"] = "1" - # On cygwin, the DLL is called cygvirtmod.dll try: import libvirtmod -- cgit