pyobjc / Install.html

Diff from to


 % python --help-commands
-<p>The following command will build and install the PyObjC package:</p>
-% python install
-<p>The system can also be used to create source and binary
-distribution archives automatically.</p>
 <p>The following command will build and open a binary installer for PyObjC,
 py2app, tools, examples, and documentation:</p>
 % python bdist_mpkg --open
-<p>If you want to install the PyObjC package without examples, documentation,
-or py2app, you can use the standard distutils install command:</p>
-% sudo python install
-<p>If you have multiple versions of Python installed on your system, the
-above will only install PyObjC for whatever version of Python is the
-default on the command line.   Make sure you are installing PyObjC
-against the correct version of Python.</p>
+<p>When multiple versions of Python are installed, the above examples
+will use the default interpreter.  Unless you have changed your
+<code><span>PATH</span></code> environment variable, this will be the Python interpreter
+that ships with Mac OS X.  To use PyObjC with an alternate Python
+interpreter, specify it explicitly or manipulate your <code><span>PATH</span></code>
+such that the location of the Python interpreter comes before
 <p>Note that there is a known bug in Python 2.3.0 
-(as shipped with Mac OS X 10.3.x), such that when another framework Python is 
-installed it will not link extensions (such as PyObjC) properly, rendering them
-unusable.  If you intend to build PyObjC for Python 2.3.0, ensure that no other
-framework Python is installed, such as a previous installation for Mac OS X
-10.2.  For more information on this and other Python issues on Mac OS X,
-please refer to the <a href=""> FAQ</a>.</p>
+(as shipped with Mac OS X 10.3), such that when another framework Python is 
+installed it will not link extensions (such as PyObjC) properly, rendering
+them unusable.  If you intend to build PyObjC for Python 2.3.0, first install
+the <a href="">PantherPythonFix</a> package from <a href="http;//"> packages</a>.</p>
 <p>If you have a previous version of PyObjC installed, you may see an exception
 such as <code><span>Wrong</span> <span>version</span> <span>of</span> <span>PyObjC</span> <span>C</span> <span>API</span></code>.  If this happens, you should
 delete any previous installation of PyObjC and the build folder in your
 new sources and try again.  PyObjC will typically be installed to a folder
-of the same name in /Library/Python/2.3 or /Library/Python/2.3/site-packages.</p>
-<p>To be able to build the wrappers for the WebKit framework (included with
-Safari 1.0) on Mac OS X 10.2, you'll have to install the WebKit SDK. You can
-download this from the <a href="">ADC website</a>.</p>
-<p>PyObjC has limited support for <a href="">GNUstep</a>. See <a href="Doc/gnustep.html">Doc/gnustep.txt</a> for 
-more information.</p>
+of the same name in <code><span>/Library/Python/2.3</span></code> or
+<p>When using Mac OS X 10.2, you must install the WebKit SDK from the
+<a href="">ADC website</a> in order to build or use
+the WebKit wrapper.</p>
 <h2><a name="examples">Examples</a></h2>
 <p>The <a href="Examples/00ReadMe.html">examples directory</a> contains a number of projects that demonstrate
 various features of the PyObjC bridge. The scripts at the top level of
 % python py2app
 % open dist/
-<p>For projects that contain a Project Builder (.pbproj), you can build them
-with Project Builder or Xcode.  Xcode (.xcode) projects can be built only
-with Xcode.  However, all examples ship with a py2app-based, and
-this is the preferred build method.</p>
+<p>The preferred method for building the examples is to use a py2app-based, as above.  Some examples may also have an Xcode (.xcode)
+or Project Builder (.pbproj) project file, but these may be out of date.</p>
+<p>All of the examples are always installed whether or not the target
+operating system supports them.  If an example fails to run due to a
+ImportError, it is likely that the example is intended for a newer
+version of Mac OS X.</p>
 <h2><a name="project-templates">Project Templates</a></h2>
-<h3><a name="xcode-on-mac-os-x-10-3">Xcode on Mac OS X 10.3</a></h3>
+<h3><a name="xcode-on-mac-os-x-10-3">Xcode on Mac OS X 10.3+</a></h3>
 <p>The <code><span>Xcode</span></code> directory contains some file and project that make it easier to
 work with Python and PyObjC when using <a href="">Xcode</a>.</p>
-<p>Copy the templates in <code><span>Xcode/File</span> <span>templates</span></code> to <code><span>/Library/Application</span> <span>Support/Apple/Developer</span> <span>Tools/File</span> <span>Templates</span></code>. Copy the templates in <code><span>Xcode/Project</span> <span>Templates</span></code> to <code><span>/Library/Application</span> <span>Support/Apple/Developer</span> <span>Tools/Project</span> <span>Templates</span></code>.</p>
-<p>There are two project templates:</p>
-<li>Cocoa-Python Application<p>A project created from this template is designed to implement standalone,
-pure-Python, applications that are compatible with Apple's build of Python as
-well as all other builds of python that support PyObjC.</p>
-<p>When building the 'install' target, the resulting application wrapper will
-include the PyObjC package and can be launched on any stock OS X 10.3 system
-without requiring PyObjC to be preinstalled.</p>
-<p>Note that the optional 'BSD Subsystem' component of Mac OS X is required,
-however it is installed by default and should be present on most systems.</p>
-<li>Cocoa-Python Document-based Application<p>This template works like the Cocoa-Python Application template in that it
-is compatible with the Apple build of Python.   It creates an application 
-that uses Cocoa's Multiple Document Architecture in the same fashion as the
-default Cocoa Document-based Application supplied with Project Builder.</p>
-<p>Note that Python applications built on Mac OS X 10.3 are not compatible with
-Mac OS X 10.2.  At this time, a Mac OS X 10.2 system must be used to build
-Mac OS X 10.2 compatible applications.</p>
+<p>For documentation on these templates, see <a href="Xcode-templates.html">Xcode-Templates.html</a></p>
+<p>Normally these Xcode templates are installed with PyObjC by the package installer.
+If doing development, you may copy or symlink them to the appropriate places in
+<code><span>/Library/Application</span> <span>Support/Apple/Developer</span> <span>Tools/</span></code>.</p>
 <h3><a name="project-builder-on-mac-os-x-10-2">Project Builder on Mac OS X 10.2</a></h3>
+<p>The Project Builder templates are out of date and unsupported.  You should
+use py2app exclusively when developing on Mac OS X 10.2.</p>
 <p>The <code><span>ProjectBuilder</span> <span>Extras</span></code> directory contains additional files that can
 be used with Project Builder. The directory <code><span>Specifications</span></code> contains files
 that enable syntax coloring for Python files in Project Builder.</p>
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.