[issue5766] Mac/scripts/BuildApplet.py reset of sys.executable during install can cause it to use wrong modules

Ned Deily added the comment: This problem was caused by a conflict between the expat parser included with Python and the expat parser included with the MacPorts ports of the obsolete pyxml package. The MacPorts project has subsequently deleted the py*-xml ports. A solution for this issue is t

[issue5766] Mac/scripts/BuildApplet.py reset of sys.executable during install can cause it to use wrong modules

Changes by Ezio Melotti : -- versions: +Python 2.7 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue5766] Mac/scripts/BuildApplet.py reset of sys.executable during install can cause it to use wrong modules

Changes by Ronald Oussoren : -- assignee: -> ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue5766] Mac/scripts/BuildApplet.py reset of sys.executable during install can cause it to use wrong modules

Ronald Oussoren added the comment: I haven't looked in this particular problem yet, but please note that the Mac-specific libraries do not work with an UCS4 build of python. -- nosy: +ronaldoussoren ___ Python tracker

[issue5766] Mac/scripts/BuildApplet.py reset of sys.executable during install can cause it to use wrong modules

Bryan Blackburn added the comment: FYI, I'm able to avoid this by using "PYTHONHOME=$(DESTDIR)$(prefix)" before $(RUNSHARED) when running BuildApplet.py and $(BUNDLEBULDER) in Mac/Makefile.in, Mac/IDLE/Makefile.in, and Mac/PythonLauncher/Makefile.in. -- __

[issue5766] Mac/scripts/BuildApplet.py reset of sys.executable during install can cause it to use wrong modules

New submission from Bryan Blackburn : With Python 2.6.1 currently installed and attempting to install 2.6.2 into a DESTDIR location, and having a different configuration for the new one (2.6.1 built with default Unicode settings, 2.6.2 with UCS4), BuildApplet.py fails because of symbol not fou