This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: sys.executable in applets
Type: Stage:
Components: macOS Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: jvr Nosy List: jackjansen, jvr
Priority: normal Keywords:

Created on 2002-10-19 21:18 by jackjansen, last changed 2022-04-10 16:05 by admin. This issue is now closed.

Messages (4)
msg12865 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2002-10-19 21:18
In applets sys.executable is the interpreter in the applet. Running this will launch a second copy of the applet. As sys.executable is apparently often used to fire up external scripts with system() or popen() this isn't very useful right now (especially within the IDE!).

It would be nice if sys.executable could be set to an interpreter that can be used for starting external scripts.
msg12866 - (view) Author: Just van Rossum (jvr) * (Python triager) Date: 2003-01-04 10:32
Logged In: YES 
user_id=92689

This becomes a non-issue once we build applets with
bundlebuilder.py, as the "executable" in the applet is a
shell script, and sys.executable will actually be the proper
executable. For standalone apps built with bundlebuilder.py
sys.executable points to the (still vanilla) interpreter
that was copied to the bundle, and can be used as a normal
interpreter without invoking bundle magic.
msg12867 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-01-04 21:23
Logged In: YES 
user_id=45365

Agreed. I'm assigning it to you, then you can close the bug report once you've modified BuildApplet to use bundlebuilder in MacPython-OSX. :-)
msg12868 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-02-12 15:50
Logged In: YES 
user_id=45365

This has been fixed in CVS.
History
Date User Action Args
2022-04-10 16:05:46adminsetgithub: 37344
2002-10-19 21:18:20jackjansencreate