cpython

History

Jack Jansen 3bbb617ca4 First stab at the launcher application. This will be run when the user doubleclicks a .py, .pyw or .pyc file. It runs the file by invoking the relevant interpreter (either the command line Python in a terminal window or a Python.app for GUI-based scripts). Interpreter to use and the options to pass are settable through preferences. If PythonLauncher wasn't running it does its thing for one script and exits. If it was manually started before a dialog is presented where the user can set the options to use, etc. To be done: - option-drag/doubleclick should always open the interactive dialog - Terminal-window isn't done yet - Should be reimplemented in Python, but pyobjc isn't part of the core. - Various menu entries should be disabled.		2002-07-29 21:36:35 +00:00
..
PythonLauncher	First stab at the launcher application. This will be run when the user	2002-07-29 21:36:35 +00:00
Mac.pth	Patch #557719 by Tony Lownds, slightly massaged by me: streamline the	2002-06-21 14:48:38 +00:00
Makefile	Got rid of symlink target, and in stead have "make dontinstallmacsubtree"	2002-07-08 13:34:23 +00:00
README	Updated, and converted line-endings to unix-style (oops:-)	2001-12-09 23:17:38 +00:00
pythonw.sh	Shell script that invokes Python.app from the command line. Called pythonw	2002-03-29 14:15:22 +00:00
sample_sitecustomize.py	Add Mac/Lib/lib-scriptpackages to sys.path too.	2002-03-30 23:43:36 +00:00

README

This directory contains a Makefile that will create a proof-of-concept
Mac OS X application for Python. The process is far from streamlined,
and it will definitely change in future releases of Python, but I wanted to
include this in the current distribution so people could play with it.

To create a fullblown Python.app proceed as follows.

1. In the main Python source directory configure python with
   configure --enable-framework
2. Do a "make clean" if you did a previous build, then "make".
3. Install this as a framework with "make frameworkinstall". This puts a Python
   framework into /Library/Frameworks.
4. Come back here (Mac/OSX) and build and install the application,
   with "make install".
5. It is probably a good idea to add the Mac-specific modules to the framework,
   with "make installmacsubtree". This puts a MacPython lib directory into
   sys.prefix/Mac/Lib. Again, this is a temporary measure.
6. To actually find the Lib directory installed in step 5 you add a line
   to your site.py file (the one in /Library/Frameworks/....):
   sys.path.append(os.path.join(sys.prefix, 'Mac/Lib'))

You are now done. In your Applications you should have a "Python", with the icon
being a falling 16 Ton weight with a shadow under it. You can drop Python scripts
on this and the will be run, in a full-windowing environment. Note that you
do not get sys.stdin, and that sys.stdout goes to the console (Use
Applications/Utilities/Console to see it).

For some reason the application only accepts files with TEXT type, not straight unix
typeless files.

Something to take note of is that the ".rsrc" files in the distribution are not
actually resource files, they're AppleSingle encoded resource files.

	Jack Jansen, jack@oratrix.com, 11-Sep-01.