[exec] tar xzf Jinja2-2.6.tar.gz
[exec] Traceback (most recent call last):
[exec] File "setup.py", line 40, in <module>
[exec] from setuptools import setup, Extension, Feature
[exec] ImportError: No module named setuptools
[exec] make: *** [/slots/03/dir_12824/userdir/pegasus/dist/pegasus-4.2.0cvs/lib/pegasus/externals/python/jinja2] Error 1
[exec] (cd Jinja2-2.6 && \
[exec] python setup.py build && \
[exec] rm -rf /slots/03/dir_12824/userdir/pegasus/dist/pegasus-4.2.0cvs/lib/python/jinja2 && \
[exec] cp -R build/lib*/jinja2 /slots/03/dir_12824/userdir/pegasus/dist/pegasus-4.2.0cvs/lib/pegasus/externals/python/ \
[exec] )

Is this only a build time dependency? Or is python-setuptools required at runtime as well?

There are several options to deal with this (there could be other solutions):

1. Remove Jinja2 from our distribution and make that a runtime dependency

2. Document this as a build time dependency. We then have to work with the Batlab people to get the dependency installed everywhere (alternatively, build python-setup tools in our Batlab scripts)