Text of wiki.python.org › python › infrastructure › TrackerDevelopment.html as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Tracker Development - Python Wiki

Python Wiki Python Wiki / Python Wiki / Infrastructure / Tracker Development View as Markdown Tracker Development ¶ Legacy Wiki Page This page was migrated from the old MoinMoin-based wiki. Information may be outdated or no longer applicable. For current documentation, see python.org . Roundup tracker has been retired in favour of GitHub issues. See https://github.com/psf/gh-migration This page is dedicated to development of Python bug tracker instance at http://bugs.python.org/ We have a meta tracker for current issues and DesiredTrackerFeatures page for recording ideas.

See also TrackerDevelopmentPlanning . Docker ¶ The simplest way to work with the tracker is by using Docker. Clone the docker-bpo repo and follow the README. If you want to install the tracker manually follow the instructions below. Requirements ¶ This configuration is deployed on production server, so it is good to stick it for development as well: Roundup 1.4.20+ (patched version) PostgreSQL (as a backend database) psycopg2 (bindings for the above) pyoidc (OpenID Connect library from https://github.com/rohe/pyoidc ) http://bugs.python.org/ ( python-dev tracker instance or configuration) is running PostgreSQL on backed, because it has the best performance for large installations.

Besides, there is at least one place in the python-dev config with hardcoded dependency on the SQL-based backed. Getting the source ¶ Get patched version of Roundup tracker from here: http://hg.python.org/tracker/roundup/ (the changes are in the bugs.python.org branch) Tracker configuration for http://bugs.python.org/ (called ‘tracker home’, ‘instance’ or `environment) is here: Official: http://hg.python.org/tracker/python-dev/ Mirror: https://bitbucket.org/rirror/bugs.python.org Other tracker configurations ¶ There are several Roundup trackers used for Python development.

Configuration for them is maintained in http://hg.python.org/tracker/ repositories: roundup : a clone of the original Roundup with our modifications; python-dev : the instance used on bugs.python.org; meta : the instance used for the meta tracker; jython : the instance used for the jython tracker; setuptools : the instance used for the setuptools tracker; rietveld : a clone of Rietveld used to do reviews on the bug tracker; django-gae2django : a clone of django-gae2django necessary for rietveld; Setup bugs.python.org instance ¶ Install patched Roundup ¶ Clone code and switch to bugs.python.org branch before installing.

Here it is installed to hardcoded system-wide location at /opt/tracker-roundup/ . Read-only clone hg clone http://hg.python.org/tracker/roundup Read/Write clone (if you have write access to the repository) hg clone ssh://hg@hg.python.org/tracker/roundup cd roundup hg up bugs.python.org sudo python setup.py install --prefix /opt/tracker-roundup/ Checkout the python-dev instance ¶ Read-only clone hg clone http://hg.python.org/tracker/python-dev Read/Write clone (if you have write access to the repository) hg clone ssh://hg@hg.python.org/tracker/python-dev Checkout the Rietveld integration (optional) ¶ If you want to work on Rietveld code review tool, check out the django-gae2django and rietveld clones in the python-dev/ directory: Read-only clone cd python-dev hg clone http://hg.python.org/tracker/django-gae2django/ hg clone http://hg.python.org/tracker/rietveld/ Read/Write clone (if you have write access to the repository) cd python-dev hg clone ssh://hg@hg.python.org/tracker/django-gae2django/ hg clone ssh://hg@hg.python.org/tracker/rietveld/ After getting the clones remember to update the branches to bugs.python.org : cd django-gae2django hg up bugs.python.org cd .. cd rietveld hg up bugs.python.org In addition, Django needs to be installed; e.g. the Django 1.2 or 1.3 Debian packages work fine.

Install psycopg2 (PostgreSQL access library for Python) ¶ For Debian/Ubuntu: sudo apt-get install python-psycopg2 For other systems, follow instructions from psycopg2 site . Install and configure PostgreSQL ¶ Other backends may work, but it is recommended to keep development environment close to production. It has been reported that 8.2, 8.3, 8.4, and 9.1 work well. See UpgradingPostgreSQL if you need to upgrade version.

Access control in PostgreSQL is tricky. You need to know Unix user, under which you run Roundup, setup access for him to PostgreSQL database, and add PostgreSQL user that you’ve configured in Roundup’s configuration. For a development environment the easiest way is to allow any user from localhost to connect as any database user. This can be accomplished by editing pg_hba.conf (usually found in /etc/postgresql/9.x/main/ in Linux or /Library/PostgreSQL/9.x/data/ in Mac OS X – you might need privileges to edit it).

The end of the file should look like this (the four changed lines are preceded by ##): # Database administrative login by UNIX sockets ##local all postgres ident local all postgres trust # TYPE DATABASE USER CIDR-ADDRESS METHOD # "local" is for Unix domain socket connections only ##local all all ident local all all trust # IPv4 local connections: ##host all all 127.0.0.1/32 md5 host all all 127.0.0.1/32 trust # IPv6 local connections: ##host all all ::1/128 md5 host all all ::1/128 trust PLEASE NOTE : This is not a secure configuration on a multi-user machine.

After the change in pg_hba.conf, reload your postgreSQL database to make sure it knows about your new access configuration. Something similar to sudo /etc/init.d/postgresql reload should do the trick on Unix-like platforms. On Mac OS X, do sudo su - postgres . Then use pg_ctl to restart the server: /Library/PostgreSQL/9.x/bin/pg_ctl restart -D /Library/PostgreSQL/9.x/data Create a database user that is allowed to create databases.

This user will be used when roundup connects to the database. $ psql -U postgres postgres=# create user roundup; postgres=# alter user roundup with createdb; Configure your Development Roundup Instance ¶ Now enter the python-dev directory, and create the ‘db’ directory, as well as the db/backend_name file which decides which backend (i.e. database type) to use: cd python-dev mkdir db echo postgresql > db/backend_name Note: the db dir contains all the messages and files attached to issues, and it’s removed and recreated every time you run roundup-admin init .

Copy python-dev/config.ini.template into config.ini and detectors/config.ini.template into detectors/config.ini : cp config.ini.template config.ini cp detectors/config.ini.template detectors/config.ini The former will let you configure your roundup instance; the latter, detectors such as irker , busybody , or tellteam . In config.ini pay special attention to settings marked with NO DEFAULT . config.ini.template already contains some useful default values for a development enviroment, for example debug = debugmail.txt at the end of the [mail] section saves outgoing mails on a local file; and debug = on at the end of the [web] section shows tracebacks in the browser instead of having them sent by email.

Initialize your roundup instance: /opt/tracker-roundup/bin/roundup-admin -i <your python-dev directory> init Provide a password for the ‘admin’ user when asked for. Note : you have to provide the full path to your python-dev directory, otherwise the command will fail. If you are getting the error: “ roundup.hyperdb.DatabaseError: FATAL: password authentication failed for user "roundup" ” check again pg_hba.conf; “ roundup.configuration.OptionUnsetError: MAIL_DOMAIN is not set and has no default ” set the option in python-dev/config.ini, [mail] section, domain; Start your roundup instance: /opt/tracker-roundup/bin/roundup-server -p 9999 python-dev=<your python-dev directory> You will have to use this command every time you (re)start roundup, so it’s easier to create an alias for it with: alias start-roundup='/opt/tracker-roundup/bin/roundup-server -p 9999 python-dev=<your python-dev directory>' It might be a good idea to creat

The rest of this page is on the live site.