Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

python(1) [osx man page]

PYTHON(1)						    BSD General Commands Manual 						 PYTHON(1)

python, pythonw -- an interpreted, interactive, object-oriented programming language SYNOPSIS
python ... pythonw ... DESCRIPTION
To support multiple versions, the programs named python and pythonw now just select the real version of Python to run, depending on various settings. (As of Python 2.5, python and pythonw are interchangeable; both execute Python in the context of an application bundle, which means they have access to the Graphical User Interface; thus both can, when properly programmed, display windows, dialogs, etc.) The current supported versions are 2.6 and 2.7, with the default being 2.6. Use % man python2.6 % man python2.7 % man pythonw2.6 % man pythonw2.7 to see the man page for a specific version. Without a version specified, % man pydoc and the like, will show the man page for the (unmodified) default version of Python (2.6). To see the man page for a specific version, use, for example, % man pydoc2.7 CHANGING THE DEFAULT PYTHON
Using % defaults write Version 2.7 will make version 2.7 the user default when running the both the python and pythonw commands (versioner is the internal name of the version- selection software used). To set a system-wide default, replace '' with '/Library/Preferences/' (admin privileges will be required). The environment variable VERSIONER_PYTHON_VERSION can also be used to set the python and pythonw version: % export VERSIONER_PYTHON_VERSION=2.7 # Bourne-like shells or % setenv VERSIONER_PYTHON_VERSION 2.7 # C-like shells % python ... This environment variable takes precedence over the preference file settings. 64-BIT SUPPORT Versions 2.6 and 2.7 support 64-bit execution (which is on by default). Like the version of Python, the python command can select between 32 and 64-bit execution (when both are available). Use: % defaults write Prefer-32-Bit -bool yes to make 32-bit execution the user default (using '/Library/Preferences/' will set the system-wide default). The environment variable VERSIONER_PYTHON_PREFER_32_BIT can also be used (has precedence over the preference file): % export VERSIONER_PYTHON_PREFER_32_BIT=yes # Bourne-like shells or % setenv VERSIONER_PYTHON_PREFER_32_BIT yes # C-like shells Again, the preference setting and environmental variable applies to both python and pythonw. USING A SPECIFIC VERSION
Rather than using the python command, one can use a specific version directly. For example, running python2.7 from the command line will run the 2.7 version of Python, independent of what the default version of Python is. One can use a specific version of Python on the #! line of a script, but that may have portability and future compatibility issues. Note that the preference files and environment variable that apply to the python command, do not apply when running a specific version of Python. In particular, running python2.6 will always default to 64-bit execution (unless one uses the arch(1) command to specifically select a 32-bit architecture). SEE ALSO
python2.6(1), python2.7(1), pythonw2.6(1), pythonw2.7(1), arch(1) BSD
Aug 10, 2008 BSD

Check Out this Related Man Page

PYTHON-MKDEBIAN(1)						   User Commands						PYTHON-MKDEBIAN(1)

python-mkdebian - Generate a suitable Debian source package for a standard distutils application SYNOPSIS
python-mkdebian [options] DESCRIPTION
This script generates a reasonably Debian Policy compliant Debian source package for a Python application that uses distutils properly. It assumes that there are no public Python modules, and generates just a single application binary package. Information is taken from's generated .egg-info file: author, project name, description, version, upstream source, license, and required and provided Python modules (which are translated to Debian python library package names, and automatically added as package dependencies). It generates a simple cdbs/python-support rules file. python-mkdebian was designed to be used with the module, which calculates required Python dependencies automatically. However, it makes no explicit assumptions about DistUtilsExtra, so if has complete information it will work with any distutils setup. OPTIONS
--force-control=FORCE_CONTROL Force control file behaviour. Can be one of "none" (keep unchanged), "deps" (only update dependencies), or "full" (recreate whole file). By default only dependencies will be updated ("deps"). --force-copyright Force whole copyright file to be recreated. By default it will not touch an already existing copyright file, so that you can custom- ize them. --force-rules Force whole rules file to be recreated. By default it will not touch an already existing rules file, so that you can customize them. --changelog=CHANGELOG Add changelog entry to debian/changelog (can be specified multiple times) --dependency=PACKAGENAME Add additional debian package dependency (can be specified multiple times) --prefix=PREFIX Ask for installing all your modules in the dedicated PREFIX (default is /usr) --version Show program's version number and exit -h, --help Show this help message and exit SEE ALSO
Python help for the distutils module AUTHOR
python-mkdebian is developed by Martin Pitt <>. python-mkdebian May 2010 PYTHON-MKDEBIAN(1)
Man Page