Bug 986153 - Always run beah in Python 2.6+
Summary: Always run beah in Python 2.6+
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: beah
Version: 0.13
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On: 810893
Blocks: 922252
TreeView+ depends on / blocked
 
Reported: 2013-07-19 05:32 UTC by Nick Coghlan
Modified: 2019-05-22 10:41 UTC (History)
10 users (show)

Fixed In Version:
Clone Of: 922252
Environment:
Last Closed: 2015-03-30 07:53:10 UTC
Embargoed:

Attachments (Terms of Use)

Description Nick Coghlan 2013-07-19 05:32:26 UTC 
Currently, we run beah in the system Python for RHEL 4+. For RHEL 3, we instead run it in a separately packaged version of Python 2.6.

This appears to be the cause of at least one bug when running in Python 2.3 on RHEL 4, and also prevents the use of more recent versions of Twisted on RHEL 5 (as RHEL 5 only provides Python 2.4, which was last supported in Twisted 11.0. At time of writing, the latest version of Twisted is 13.1).

This issue covers switching to using separately packaged versions of Python and other dependencies on RHEL 4 and RHEL 5 as well as on RHEL 3.

This change will mean that beah will always run in at least Python 2.6 (since the system Python in RHEL 6 is also 2.6) and may run in Python 2.7 (as that is the system Python in Fedora and RHEL 7+).
Comment 1 Nick Coghlan 2013-10-01 07:05:54 UTC 
Switched order of dependency relative to bug 810893, since running on an upstream Twisted in an alternative harness is lower impact than always running on a system independent Python installation
Comment 3 Dan Callaghan 2015-03-30 07:53:10 UTC 
At this point I think it makes more sense to focus on improving restraint instead.
Note You need to log in before you can comment on or make changes to this bug.