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
INSTALL>
pypm install pundler

How to install Pundler

  1. Download and install ActivePython
  2. Open Command Prompt
  3. Type pypm install pundler
 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
0.0.2 Available View build log
Windows (64-bit)
0.0.2 Available View build log
Mac OS X (10.5+)
0.0.2 Available View build log
Linux (32-bit)
0.0.2 Available View build log
Linux (64-bit)
0.0.2 Available View build log
 
Author
Dependencies
Imports
Lastest release
version 0.0.2 on Jun 16th, 2013

About

Pundler is an attempt to better manage python requirements files.

Pundler is inspired by Ruby's Gem Bundler.

Specifically the goal is to process requirements.in or requirements.txt into a frozen lock file similar to Gemfile and Gemfile.lock in the ruby world.

The advantage of doing something like this is that your requirements file specifies only versions of things that you specifically depend on and dependencies brought in by those dependencies can be easily identified and separated out.

For example, if I install the requirement jinja2==2.7 I don't actually care about also installing jinja2's dependency markupsafe but it will be installed. By running Pundler I end up with a nicely pinned requirements.txt that I can just regenerate from my "real" requirements.in whenever requirements I actually care about change.

For example, say I have in requirements.in:

a==1.0
b==2.0
c==3.0

And if we include the dependencies of those packages we have:

a==1.0
adep1==1.0
adep2==1.0
b==2.0
bdep1==2.0
c==3.0

Say we eventually upgrade a to version 2.0:

a==2.0
adep1==1.0
adep2==1.0
b==2.0
bdep1==2.0
c==3.0

In a==2.0 the dependency adep1==1.0 is no longer needed. If we have one requirements file with all versions pinned it isn't clear that that dependency can now be removed.

If instead we simply updated the original requirements.in we could regenerate the full requirements (as a requirements.txt) and it would be clear that adep1==1.0 was no longer required.

Usage

Simply run pundler in a directory with your requirements.in:

python setup.py develop
pundler

Pundler will process the file and create a requirements.txt that has all packages pinned to specific versions and identifies clearly what depends on what packages depend on what.

Example

Given the following requirements.example.in:

pyramid==1.4.2
jinja2
txtemplate

Pundler will generate the this requirements.example.txt:

# requirement 'pyramid==1.4.2' depends on:
WebOb==1.2.3
pyramid==1.4.2
translationstring==1.1
repoze.lru==0.6
Mako==0.8.1
MarkupSafe==0.18
PasteDeploy==1.5.0
Chameleon==2.11
venusian==1.0a8
zope.deprecation==4.0.2
zope.interface==4.0.5
setuptools==0.6c11

# requirement 'jinja2' depends on:
jinja2==2.7
markupsafe==0.18

# requirement 'txtemplate' depends on:
genshi==0.7
#jinja2==2.7
twisted==13.0.0
#markupsafe==0.18
txtemplate==1.0.2
#zope.interface==4.0.5
#setuptools==0.6c11

Subscribe to package updates

Last updated Jun 16th, 2013

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.