Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

Download
ActivePython

pippy is unavailable in PyPM, because there aren't any builds for it in the package repositories. Click the linked icons to find out why.

 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
0.1.0 Failed View build log
Windows (64-bit)
0.1.0 Failed View build log
Mac OS X (10.5+)
0.1.0 Failed View build log
Linux (32-bit)
0.1.0 Failed View build log
Linux (64-bit)
0.1.0 Failed View build log
 
Links
License
MIT
Dependencies
Lastest release
version 0.1.0 on May 23rd, 2012

pippy is a pip extension that will allow you to keep local copies of prebuilt python packages. It's main purpose is to be used with virtstrap so that virtstrap can create copies of each project without ever having to download or build anything. It accomplishes this only when it knows the exact version of the package you wish to download. Otherwise it behaves just as pip would behave.

Since virtstrap generates a VEfile.lock (similar to Ruby Bundler's Gemfile.lock). Virtstrap tracks the exact version of the software you're using. For this very reason, pippy is planned to be included in virtstrap.

Local Package Storage

By default pippy stores all of the packages in ~/.pippy. To change this directory just change the environment variable PIPPY_CACHE to point to the desired directory. The folder structure for the storage is this:

~/.pippy
    packages/
        source/ # <- stores the sources for packages
            package-name/
                .. tons of zips/tars ..
            package-name/
            package-name/
        cpython/ # <- stores builds for cpython
            2.5/    # <- stores builds for python 2.5
                package-name/
                    .. tons of tars ..
            2.6/    # <- for python 2.6
            ... more python versions ...
        pypy/ # <- stores builds for pypy
        ... more implementations ...

The CLI currently only accepts one argument, a pip requirements file:

pippy [requirementsfile]

It is highly suggested that the requirements file use only exact specifications for the requirements.

Further Development

Eventually, pippy will provide almost the same commands as pip, plus some additional commands for managing the installed packages.

Future Commands
  • install - Will work the same as pip install
  • manage - Will manage all the packages in pippy's cache.
  • uninstall - A convenience operation to pip's uninstall command

Known Issues

These issues will be rectified as soon as possible

  • Doesn't adequately support custom package indexes. It'll work, but it's use is highly discouraged at this time.
  • Isn't known to work with Windows

Subscribe to package updates

Last updated May 23rd, 2012

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.