##
3.4 Alternate installation: Mac OS

Like Windows, Mac OS has no notion of home directories (or even of users), and a fairly simple standard Python installation. Thus, only a --prefix option is needed. It defines the installation base, and files are installed under it as follows:

** how do MacPython users run the interpreter with command-line args? **

Type of file | Installation Directory | Override option
--- | --- | ---
pure module distribution | prefix:Lib | --install-purelib
non-pure module distribution | prefix:Mac:PlugIns | --install-platlib
scripts | prefix:Scripts | --install-scripts
data | prefix:Data | --install-data

** Corran Webster says: ``Modules are found in either :Lib or :Mac:Lib, while extensions usually go in :Mac:PlugIns''--does this mean that non-pure distributions should be divided between :Mac:PlugIns and :Mac:Lib? If so, that changes the granularity at which we care about modules: instead of ``modules from pure distributions'' and ``modules from non-pure distributions'', it becomes ``modules from pure distributions'', ``Python modules from non-pure distributions'', and ``extensions from non-pure distributions''. Is this necessary?!? **