"easy_install py"

With a working setuptools installation you can type:

easy_install -U py

to get the latest release of the py lib. The -U switch will trigger an upgrade if you already have an older version installed. The py lib and its tools are expected to work well on Linux, Windows and OSX, Python versions 2.3, 2.4, 2.5 and 2.6.

We provide binary eggs for Windows machines.

On other systems you need a working C-compiler in order to install the full py lib. If you don't have a compiler available you can still install the py lib but without greenlets - look below for the install_lib target.

IMPORTANT NOTE: if you are using Windows and have previous installations of the py lib on your system, please download and execute http://codespeak.net/svn/py/build/winpathclean.py This will check that no previous files are getting in the way. (Unfortunately we don't know about a way to execute this code automatically during the above install).

Installing on Debian or Fedora

As of July 2009 pytest/pylib 1.0 RPMs and Debian packages are not yet available.

On Debian systems look for python-codespeak-lib. This package is probably outdated - if somebody can help with bringing this up to date, that would be very much appreciated.

Dwayne Bailey has thankfully put together a Fedora RPM.

Downloading a tar/zip archive and installing that

You need a working setuptools installation.

Go to the python package index (pypi) and download a tar or zip file:

http://pypi.python.org/pypi/py/

and unpack it to a directory, where you then type:

python setup.py install

Installing from subversion / develop mode

To follow development or help with fixing things for the next release, checkout the complete code and documentation source with mercurial:

hg clone https://bitbucket.org/hpk42/py-trunk/

or with subversion:

svn co http://codespeak.net/svn/py/trunk

With a working setuptools installation you can then issue:

python setup.py develop

in order to work with your checkout version.

Working with multiple py lib versions / svn externals

If you happen to have multiple versions of the py lib around or you ship the py lib as an svn-external to then you might want to use py lib scripts more directly. For example if you have a project layout like this:

mypkg/
    subpkg1/
        tests/
    tests/
py/ # as svn-external, could be specific tag/version

then you want to make sure that the actual local py lib is used and not another system-wide version. For this you need to add py/bin or py\bin\win32 respectively to your system's PATH settings.

You can do this by executing (on windows) a script to set the environment:

c:\\path\to\checkout\py\env.cmd

or on linux/osx you can add something like this to your shell initialization:

eval `python ~/path/to/checkout/py/env.py`

to get good settings for PYTHONPATH and PATH.