This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

What is MinistryOfPackages?

A simple Python package index server implementation, meant for internal use (at least for now). The expectation is that it runs behind a firewall, and also most likely a reverse proxy. It requires PyYAML and Tornado (, and it’s tested with pip and Python 2.7 It is not tested with easy_install, and easy_install support is not a near-term goal or priority (Please use pip)

What Works Now?

Right now, MinistryOfPackages is usable for simple use cases:

  1. It has DirectoryListing support, and that’s completely generic. It’s meant to be used by command line tools, but the browser presentation works – it just doesn’t have all the fancy icons :)

  2. You can do, for example, ‘python sdist upload -r http://localhost:8080/dist’, and then leverage the directory listing capability to go to http://localhost/packages and browse to confirm your package made it into the repository.

  3. You can ‘pip install -i http://localhost:8080/packages <pkg>’ on the package you uploaded in point 2 above.

  4. If you want to check internal first and fall back to, there’s no global pip config file (yet), so you need to export two environment variables, either in your personal shell init, or in the global shell initialization files:

    PIP_INDEX_URL=http://your.index.internal/packages PIP_EXTRA_INDEX_URL=

These features still need more testing and a little polish, but they generally work.

What’s Up Next?

  1. Completion of a data model (using Redis) to support more of the CLI and browser UI features (like ‘register’).
  2. Fleshing out a proper browser interface.

What’s After That?

  1. Proxying requests to PyPI for pip, so MinistryOfPackages can be your primary index server for everything.
  2. Package caching.
  3. PyPI Mirroring (this can technically be done now, but it’s not a good solution as it stands).

Feature requests, new ideas, and pull requests are welcome.

Why are you doing this?

I’m after a few different things with this project:

  1. I want something that’s blindingly easy to deploy. I don’t want to muck with WSGI, CGI, FCGI, whatever. I want to write code and run it, and have something that works. Having used Tornado for numerous other projects (some ‘web scale’), I can tell you it works :)
  2. I want some enterprise-y features like proxy requests and package caching. Those will come later, but I didn’t want to start this using a huge multi-headed framework because I want to get to them sooner than later :)
  3. I want to understand distutils, Python package distribution, and all that stuff better.
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
MinistryOfPackages-0.9.5.tar.gz (13.0 kB) Copy SHA256 Checksum SHA256 Source Sep 19, 2011

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting