Installation Documentation

Install Release

Install Trunk

Let me explain how we develop, so you can understand how to run Pida. Pida has a normal mode, and a development mode. Starting it with ./run-pida.py from the checkout causes it to go into development mode, which auto-adds the externals to the pythonpath, and it auto-adds the pida-plugins dir to the plugin search path. This helps developing with the latest tools while the system packages lag behind. If you intend to install pida from trunk, you have to make sure to install each package from externals and have to make sure that it do not conflict with your distribution packages — this can cause strange errors… Running in developer mode, it makes sure that you use the right packages.

Requirements for different Linux distros

warning might be incomplete, please tell us if we missed something

we assume you know basic package-management

everyone

bzr git mercurial setuptools pygtkhelpers argparse

a very recent bpython for the python shell (even the one in lucid is too old)

debian/ubuntu

base

python-gtk2 python-gtk2-dev python-vte python-dbus python-simplejson python-setuptools build-essentials python-argparse ? more?

vim

gvim

emacs

emacs-snapshot

medit

See MooEditorLinux

fedora/red-hat

warning new see  http://groups.google.com/group/pida/browse_thread/thread/85bd1b2e0980ab43

base

pygtk2-devel gcc dbus-python-devel gtk2-devel more?

vim

gvim

On All Platforms

Getting sources and source dependencies:

hg clone https://bitbucket.org/aafshar/pida-main/ pida
cd pida
./tools/update_externals.sh

Compile:

python setup.py build_ext --inplace

Now you can run pida via:

bin/pida