Closed
Bug 500692
Opened 15 years ago
Closed 15 years ago
Upgrade python on khan to at least 2.5
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: clouserw, Assigned: fox2mike)
Details
There has been talk of upgrading python but I'm not sure what the status is. I searched for a bug but came up with nothing so I'm filing this one. We need at least python 2.5 to use the silme library for some stuff with AMO. I don't know the status of other projects though so if this was installed parallel with 2.4 it would be fine with me (we've done parallel installs of 2.3 and 2.4 before). I expect to file a bug to upgrade python on the AMO cluster sometime in mid July when we are ready to start pushing these changes out.
Reporter | ||
Updated•15 years ago
|
Summary: Upgrade to python on khan to at least 2.5 → Upgrade python on khan to at least 2.5
Comment 1•15 years ago
|
||
If we can get to 2.6 we can at least keep ourselves up to date - alot of new things are in 2.6 that aren't backward compatible in 2.5 that I'd like to have the option of using. If only to get us writing 3.0 compatible code when possible.
Updated•15 years ago
|
Assignee: server-ops → shyam
Assignee | ||
Comment 2•15 years ago
|
||
Dave, Wil, I've put in python-2.6.2 on Khan. The system still has Python 2.4 to make sure the RHEL stuff that depends on Python doesn't break. So to use 2.6, you'd run python26 as shown : # python Python 2.4.3 (#1, Sep 17 2008, 16:04:01) [GCC 4.1.2 20071124 (Red Hat 4.1.2-41)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> # python26 Python 2.6.2 (r262:71600, Jun 1 2009, 20:55:03) [GCC 4.1.2 20080704 (Red Hat 4.1.2-44)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> Lemme know if you need anything else.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•15 years ago
|
||
Thanks Shyam.
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•