This repository has been archived by the owner. It is now read-only.
This PyPI is no more! See
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github PyPI is dead, long live PyPI. Apr 18, 2018
doc merge Dec 10, 2013
static one more Jul 21, 2017
templates password resets using warehouse only Apr 14, 2018
tests kill some more dead code and stuff Jul 1, 2017
tools kill some more dead code and stuff Jul 1, 2017
.cvsignore merge Dec 10, 2013
.gitignore Add a `.gitignore` file, ignore `.pyc` Aug 3, 2016
.hgignore add .idea to ignore Apr 13, 2015
CHANGES.txt merge Dec 10, 2013
LICENSE.txt merge Dec 10, 2013 add ability to configure TLS and Authentication for sending PyPI mail Nov 28, 2013
Makefile Remove unsupported code for updating SSH keys Oct 17, 2017
README.rst PyPI is dead, long live PyPI. Apr 18, 2018
TODO.txt merge Dec 10, 2013 merge Dec 10, 2013 kill some more dead code and stuff Jul 1, 2017 fixup adapter for authomatic Jul 8, 2017 merge Dec 10, 2013
config.ini.template Remove unsupported code for updating SSH keys Oct 17, 2017 Remove unsupported code for updating SSH keys Oct 17, 2017 more robust grabbing of blacklist conf Oct 19, 2016
disposable_email_blacklist.conf blacklist disposable email addresses from creating accounts Oct 19, 2016 datadogify pypi Jul 22, 2017 merge Dec 10, 2013
favicon.ico favicon needs to be in the root Feb 9, 2014 merge Dec 10, 2013 correct typo in fncache.purge Nov 26, 2017 merge Dec 10, 2013 Upgrade password handling libraries Dec 1, 2016 merge Dec 10, 2013
mirrors.txt merge Dec 10, 2013
mod_python.conf merge Dec 10, 2013
pkgbase_schema.sql fix deleting of users Jul 2, 2014
pypi.cgi Make the config.ini file relative Nov 17, 2013
pypi.fcgi Make directories (and other files) group-writable. Jan 2, 2010 Make the config.ini file relative Nov 17, 2013
pypi.wsgi add openid_claim path Jul 9, 2017 merge Dec 10, 2013 datadogify pypi Jul 22, 2017
requirements.txt upgrade packaging Jul 22, 2017 don't issue so many dang queries to construct urls Mar 23, 2018 merge Dec 10, 2013 Make the config.ini file relative Nov 17, 2013 remove project maintenance Mar 23, 2018 use Fastly-Key instead of X-Fastly-Key Jul 19, 2016 merge Dec 10, 2013 merge Dec 10, 2013 destroy documentation using warehouse now Mar 25, 2018



This repository houses the deposed codebase that powered for nearly 15 years.

warehouse now powers, the next-generation PyPI!

Required packages

To run the PyPI software, you need Python 2.7+ and PostgreSQL

Quick development setup

It is recommended to read though this document is quite out of date, but contain some useful informations.

Make sure you have a working PostgreSQL Database Available, by getting a local development install of _Warehouse_. See the Database Setup Below.

Make sure your config.ini is up-to-date, initially copying from config.ini.template. Change CONFIG_FILE at the beginning of pypi.wsgi, so it looks like this:

CONFIG_FILE = 'config.ini'

Then, you can create a development environment like this, if you have virtualenv installed:

$ virtualenv --no-site-packages .
$ pip install -r requirements.txt

Then you can launch the server using the pypi.wsgi script:

$ python pypi.wsgi
Serving on port 8000...

PyPI will be available in your browser at http://localhost:8000

Database Setup



These instruction are in progress.

Connect Legacy-PYPI to warehouse

It is highly recommended, and simpler to connect legacy-pypi to an already working warehouse setup.

Once you have a working warehouse setup, it should expose the PostgreSQL database on port 5433, you can check that in the docker-compose.yml file which should contain a ports section like so:

  image: postgres:9.5
      - "5433:5433"

Modify the pypi-legacy config.ini [database] section to connect to this database, You can find the required information as follows. In the docker-compose.yml file find the line the set the DATABASE_URL:

DATABASE_URL: postgresql://postgres@db/warehouse

It is structure in the following way: DATABASE_URL: postgresql://<user_name>@<host>/<database_name>

Use the docker-machine env to find the Docker IP, for example:

$ docker-machine env
export DOCKER_HOST="tcp://"
export DOCKER_CERT_PATH="$HOME/.docker/machine/machines/default"
export DOCKER_MACHINE_NAME="default"

Here the docker-ip is

The final config.ini will be like:


;Postgres Database using
;warehouse's docker-compose
host =
port = 5433
name = warehouse
user = postgres

Start warehouse as usual before starting PyPI-legacy, then start pypi-legacy that should now connect to the local warehouse database.

Run a local Postgres Database

It is recommended not to use a local PostgreSQL database as all the Database migration and maintenance tasks are performed by warehouse.

To fill a database, run pkgbase_schema.sql on an empty Postgres database. Then run tools/demodata to populate the database with dummy data.

To initialize an empty Postgres Database, after making sure Postgres is installed on your machine, change to a directory of your convenience, like the root of this repository, and issue the following:

$ mkdir tmp
$ chmod 700 tmp
$ initdb -D tmp

The initdb step will likely tell you how to start a database server; likely something along the line of:

$ pg_ctl -D tmp -l logfile start

You want to start that in a separate terminal, in the folder where you created the previous tmp directory, and run the above command.

Back to our initial terminal use the following to list all available Postgres databases:

$ psql -l
   Name    | Owner    | Encoding |   Collate   |    Ctype    |  Access privileges
 postgres  | guido_vr | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 template0 | guido_vr | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/guido_vr     +
           |          |          |             |             | guido_vr=CTc/guido_vr
 template1 | guido_vr | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/guido_vr     +
           |          |          |             |             | guido_vr=CTc/guido_vr

Your exact input will differ. Note the _name_ of the database. In our case above, postgres, and the _user_ name. In our case guido_vr, they will be of use to configure the database in the config.ini file later.

We now need to populate the database with an example data. For example, example.sql that can be found on the warehouse repository. After having it downloaded and unpacked, use the following:

$ pgsql -d postgres -f /path/to/example/file.sql

Where postgres is the _name_ of the database noted above.

Set up the config.ini file [database] section, to connect to the Postgres instance we just started:


;Postgres Database
host = localhost
port = 5433
name = postgres
user = guido_vr

The default _host_ is likely localhost, and the _port_ number 5433 as well. adapt name and user with the value noted before.



Usage of the SqLite local database is not recommended; And might not be functional.

For testing purposes, run the following to create a packages.db file at the root of the repository:

python2 tools/

Set [database]driver to sqlite3 in config.ini, and [database]name to packages.db:


driver = sqlite3
name = package.db

Then run tools/demodata to populate the database.

PyPI Requires the citext extension to be installed.

TestPyPI Database Setup

testpypi runs under postgres; because I don't care to fill my head with such trivialities, the setup commands are:

createdb -O testpypi testpypi
psql -U testpypi testpypi <pkgbase_schema.sql

Restarting PyPI

PyPI has 2 different pieces that need started, web server and the task runner.

# Restart the web server
$ /etc/init.d/pypi restart
# Restart the task runner
$ initctl restart pypi-worker

Clearing a stuck cache

Users reporting stale data being displayed? Try:

curl -X PURGE

(where the URL is the relevant one to the issue, I presume)

To see what fastly thinks it knows about a page (or how it's getting to you) try:

curl -I -H 'Fastly-Debug: 1'