Hide Forgot
Description of problem: The version of python-turbojson in RHEL6.0 does not understand how to return two basic SQLAlchemy types: RowProxy and ResultProxy. This makes working with SQLAlchemy in TurboGears less than ideal (and SQLAlchemy is the default ORM in TurboGears) as the individual applications need to have code that processes these two types instead of relying on the framework to do this. An update to pyhton-turbojson will bring in the upstream fix for this. Version-Release number of selected component (if applicable): python-turbojson-1.2.1-8.1.el6.noarch How reproducible: 100% Steps to Reproduce: 1. rpm -q python-turbojson 2. 3. Actual results: python-turbojson-1.2.1-8.1.el6.noarch Expected results: python-turbojson-1.3-2.el6.noarch Additional info: Upstream TurboGears has a hard requirement on the updated version of turbojson. The EPEL6 TurboGears package works around that by creating a forward compat package for python-turbojson1.3. When this package is updated EPEL6 can drop that package. The current Fedora 14 package contains a backport of the turbojson commit that adds sqlalchemy support to turbojson. This is another way to enable this functionality without upgrading the base package (the upgrade to the base package also includes changes to the code for compatibility with a newer upstream python-peak-rules package and simplifications to the code). The new python-turbojson has a requirement on a newer python-peak-rules snapshot. Updating to the version listed as required is safe but unnecessary (we have the patches equivalent to that snapshot in our python-peak-rules package). Updating python-peak-rules further than that minimum level would need to be evaluated, though, as there's some API changes sometime after that version. (I've audited the source code/SCM repositories to find all this out.)
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
I'm happy to have this evaluated for 6.1, 6.2, or a later RHEL-6 release. if this is a no for any 6.x release, please specify that in a reply. Thank you.
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.