Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #239
Difficulty: Easy
In March 1970, the ARPANET reached the East Coast of the United States, when an IMP at the Department of Energy in Washington, DC was connected to the network.
True or False?
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-CONFIG(1)					      General Commands Manual						  PYTHON-CONFIG(1)

python-config - output build options for python C/C++ extensions or embedding SYNOPSIS
python-config [ --prefix ] [ --exec-prefix ] [ --includes ] [ --libs ] [ --cflags ] [ --ldflags ] [ --extension-suffix ] [ --configdir ] [ --help ] DESCRIPTION
python-config helps compiling and linking programs, which embed the Python interpreter, or extension modules that can be loaded dynamically (at run time) into the interpreter. OPTIONS
--cflags print the C compiler flags. --ldflags print the flags that should be passed to the linker. --includes similar to --cflags but only with -I options (path to python header files). --libs similar to --ldflags but only with -l options (used libraries). --prefix prints the prefix (base directory) under which python can be found. --exec-prefix print the prefix used for executable program directories (such as bin, sbin, etc). --extension-suffix print suffix used for extension modules (including the _d modified for debug builds). --configdir prints the path to the configuration directory under which the Makefile, etc. can be found). --help print the usage message. EXAMPLES
To build the singe-file c program prog against the python library, use gcc $(python-config --cflags --ldflags) progr.cpp -o progr.cpp The same in a makefile: CFLAGS+=$(shell python-config --cflags) LDFLAGS+=$(shell python-config --ldflags) all: progr To build a dynamically loadable python module, use gcc $(python-config --cflags --ldflags) -shared -fPIC progr.cpp -o SEE ALSO
python (1) /usr/share/doc/python/faq/extending.html AUTHORS
This manual page was written by Johann Felix Soden <> for the Debian project (and may be used by others). November 27, 2011 PYTHON-CONFIG(1)

Featured Tech Videos