@@ -14,10 +14,20 @@ \section{\module{MacOS} ---
1414artifact.
1515
1616\begin {datadesc }{runtimemodel}
17- Either \code {'ppc'}, \code {'carbon'} or \code {'macho'}. This
18- signifies whether this Python uses the classic (InterfaceLib style)
19- runtime model, the Mac OS X compatible CarbonLib style or the Mac OS
20- X-only Mach-O style.
17+ Either\code {'carbon'} or \code {'macho'}. This
18+ signifies whether this Python uses the Mac OS X and Mac OS 9 compatible
19+ CarbonLib style or the Mac OS
20+ X-only Mach-O style. In earlier versions of Python the value could
21+ also be \code {'ppc'} for the classic Mac OS 8 runtime model.
22+ \end {datadesc }
23+
24+ \begin {datadesc }{linkmodel}
25+ The way the interpreter has been linked. As extension modules may be
26+ incompatible between linking models, packages could use this information to give
27+ more decent error messages. The value is one of \code {'static'} for a
28+ statically linked Python, \code {'framework'} for Python in a Mac OS X framework,
29+ \code {'shared'} for Python in a standard unix shared library and
30+ \code {'cfm'} for the Mac OS 9-compatible Python.
2131\end {datadesc }
2232
2333\begin {excdesc }{Error}
@@ -136,3 +146,15 @@ \section{\module{MacOS} ---
136146semantics, but it is not a Python file object, so there may be subtle
137147differences.
138148\end {funcdesc }
149+
150+ \begin {funcdesc }{WMAvailable}{}
151+ Checks wether the current process has access to the window manager.
152+ The method will return \code {False} if the window manager is not available,
153+ for instance when running on Mac OS X Server or when logged in via ssh,
154+ or when the current interpreter is not running from a fullblown application
155+ bundle. A script runs from an application bundle either when it has been
156+ started with \program {pythonw} in stead of \program {python} or when running
157+ as an applet.
158+
159+ On Mac OS 9 the method always returns \code {True}.
160+ \end {funcdesc }
0 commit comments