Description of problem: Your latest patch of bccache.py is not compatible with python in EPEL5. Version-Release number of selected component (if applicable): python-jinja2-2.2.1-2.el5 How reproducible: always Steps to Reproduce: 1. python 2. import jinja2 Actual results: [root@mail ~]# python Python 2.4.3 (#1, Jan 9 2013, 06:47:03) [GCC 4.1.2 20080704 (Red Hat 4.1.2-54)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import jinja2 Traceback (most recent call last): File "<stdin>", line 1, in ? File "/usr/lib64/python2.4/site-packages/jinja2/__init__.py", line 44, in ? from jinja2.bccache import BytecodeCache, FileSystemBytecodeCache, \ File "/usr/lib64/python2.4/site-packages/jinja2/bccache.py", line 213 except OSError as e: ^ SyntaxError: invalid syntax Expected results: no error Additional info: This simple patch should fix this problem for python-2.4: --- bccache.py 2014-07-01 07:36:57.000000000 +0200 +++ bccache.pyx 2014-07-01 07:36:57.000000000 +0200 @@ -210,7 +210,7 @@ actual_dir = os.path.join(tmpdir, dirname) try: os.mkdir(actual_dir, stat.S_IRWXU) # 0o700 - except OSError as e: + except OSError, e: if e.errno != errno.EEXIST: raise
Oops. Thanks for the heads-up!
python-jinja2-2.2.1-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/python-jinja2-2.2.1-3.el5
Package python-jinja2-2.2.1-3.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing python-jinja2-2.2.1-3.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1941/python-jinja2-2.2.1-3.el5 then log in and leave karma (feedback).
python-jinja2-2.2.1-4.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/python-jinja2-2.2.1-4.el5
python-jinja2-2.2.1-4.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.