This is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1121240, but jinja2 is in base/updates on RHEL6, hence the separate issue. Please close and link to the original issue if I have done this in error.
Description of problem:
Missing dep results in jinja2.__version__ to evaluate to "unknown"
100% of the time on a box without python-setuptools
Steps to Reproduce:
1. Install python-jinja2
2. Run the command: python -c 'import jinja2; print(jinja2.__version__)'
The command returns "unknown"
The command should return the version of Jinja2, "2.2.1"
I'm guessing this bug exists on RHEL7 too (though I haven't had a chance to test), should I file a separate bug for that?
This indeed is a bug and the suggested solution is correct - we should add python-setuptools as a runtime requirement to python-jinja2.
Note, that this is *not* a problem on RHEL 7, since in version 2.7.2, jinja doesn't specify version using setuptools anymore, but rather uses simple
__version__ = '2.7.2'
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.