Software: Apache/2.0.54 (Unix) mod_perl/1.99_09 Perl/v5.8.0 mod_ssl/2.0.54 OpenSSL/0.9.7l DAV/2 FrontPage/5.0.2.2635 PHP/4.4.0 mod_gzip/2.0.26.1a 

uname -a: Linux snow.he.net 4.4.276-v2-mono-1 #1 SMP Wed Jul 21 11:21:17 PDT 2021 i686 

uid=99(nobody) gid=98(nobody) groups=98(nobody) 

Safe-mode: OFF (not secure)

/usr/doc/python-2.2.3/html/mac/   drwxr-xr-x
Free 318.37 GB of 458.09 GB (69.5%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     IDEapplet.html (4.36 KB)      -rw-r--r--

Macintosh Library Modules

Previous: 1.6.3 Executing a script Up: 1.6 The IDE Next: 1.7 Configuration

---

 
1.6.4 ``Save as'' versus ``Save as Applet''

When you are done writing your Python script you have the option of saving it as an ``applet'' (by selecting ``Save as applet'' from the ``File'' menu). This has a significant advantage in that you can drop files or folders onto it, to pass them to the applet the way command-line users would type them onto the command-line to pass them as arguments to the script. However, you should make sure to save the applet as a separate file, do not overwrite the script you are writing, because you will not be able to edit it again.

Accessing the items passed to the applet via ``drag-and-drop'' is done using the standard sys.argv mechanism. See the general documentation for more

Note that saving a script as an applet will not make it runnable on a system without a Python installation.

---

Macintosh Library Modules

Previous: 1.6.3 Executing a script Up: 1.6 The IDE Next: 1.7 Configuration

---

Release 2.2.3, documentation updated on 30 May 2003.