Closed
Bug 785137
Opened 12 years ago
Closed 9 years ago
[mkt] Move zamboni to Python 2.7
Categories
(Cloud Services :: Operations: Marketplace, task, P3)
Cloud Services
Operations: Marketplace
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: andy+bugzilla, Assigned: jason)
References
Details
(Whiteboard: clouserw=p6)
Zamboni has been on 2.6 too long. Can we upgrade to Python 2.7? If so, what do we need to do make this happen?
Updated•12 years ago
|
Assignee: server-ops → oremj
Comment 1•12 years ago
|
||
Work is happening at https://github.com/oremj/rhel6-python2.7-specs/
Updated•12 years ago
|
Severity: normal → enhancement
Reporter | ||
Comment 2•12 years ago
|
||
Django 1.5 will come with Python 3 support. Is it worth skipping straight up to Python 3 instead?
Comment 3•12 years ago
|
||
Not sure if trolling or serious. It is experimental support and not recommended for production.
Comment 4•12 years ago
|
||
I would love to jump to py3k, but I feel like our 122 dependencies* might have something to say about it. Can we create a Jenkins job that builds marketplace on python 2.7? The general consensus** seems to be that "everything" works in python 2.7 as-is. Seeing what's not working would be a good first step to getting this bug out of the way. * `pip freeze | wc -l` ** Sample size of 2
Reporter | ||
Comment 5•12 years ago
|
||
Not being too serious. Unless its an awful lot of work for IT and is many months out. If we are looking at moving to python 2.7 by say Q2 2013... it feels python 3 might be a better bet.
Comment 6•12 years ago
|
||
I had the very same discussion years ago for another app. I would not hold my breath for py3 in 2013. I suspect it'll become mainstream after 2014/15 - the library ecosystem is so big and py3 does not have any killer feature that makes it appealing for the community to do the jump. I think the best bet is to move things to py 2.7 and make our code py3-friendly.
Comment 7•11 years ago
|
||
Ping, any word on this?
Comment 8•11 years ago
|
||
RHEL 7 should be out in the next 6 months or so and will ship with python 2.7. Can we close this WONTFIX and wait for RHEL 7?
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 9•11 years ago
|
||
We still need to move to RHEL 7 though.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 10•11 years ago
|
||
RHEL 7 is still not out in beta and Red Hat still has no information on when a general release might happen. Can we explore simply compiling our own Python binaries? It's doubtful that we'll be on RHEL 7 by Q2 2014.
Comment 11•11 years ago
|
||
What's the priority on this? Maintaining our own python 2.7 binaries and app dependency rpms is going to be a pretty big project.
Reporter | ||
Comment 12•11 years ago
|
||
"Python 2.6 is now in security-fix-only mode; no new features are being added, and no new bug fix releases are planned. We intend to provide source-only security fixes for the Python 2.6 series until October 2013 (five years after the 2.6 final release)" http://www.python.org/download/releases/2.6.8/ Python 2.7 is now 3 years old and contains multiple security and performance fixes. Pretty soon the security and maintenance issues are going to become ours, for example Django won't support 2.6 from version 1.7 (currently on 1.5, 1.6 is coming up soon): https://docs.djangoproject.com/en/dev/faq/install/
Comment 13•11 years ago
|
||
In the name of not having to put a version number next to Python experience on my LinkedIn profile, this is a very big priority.
Comment 14•11 years ago
|
||
(In reply to Andy McKay [:andym] from comment #12) > "Python 2.6 is now in security-fix-only mode; no new features are being > added, and no new bug fix releases are planned. We intend to provide > source-only security fixes for the Python 2.6 series until October 2013 > (five years after the 2.6 final release)" > > http://www.python.org/download/releases/2.6.8/ > > Python 2.7 is now 3 years old and contains multiple security and performance > fixes. Pretty soon the security and maintenance issues are going to become > ours, for example Django won't support 2.6 from version 1.7 (currently on > 1.5, 1.6 is coming up soon): > > https://docs.djangoproject.com/en/dev/faq/install/ RHEL will backport all security fixes to, so we won't have to worry about maintenance issues, and I expect we'll see a python 2.7 release on RHEL 7 or on RHEL 6 before Django requires it. That being said, I also would like python 2.7, but it's a non-trivial amount of work to build python 2.7.5 against RHEL, rebuild and rewrite the specs all of our dependency RPMs with the new libraries, and redo that process every time there is a feature/security release. I'll poke redhat and try to get some sort of time frame one when they will be releasing 2.7. If we don't get a satisfactory response, we'll start working on this.
Comment 15•11 years ago
|
||
(In reply to Jeremy Orem [:oremj] from comment #14) > RHEL will backport all security fixes to, RHEL will backport all security fixes to 2.6,
Comment 16•11 years ago
|
||
We have the ability to use python 2.7 now via Redhat's "Software Channels". How would you all like to proceed with this?
Comment 18•11 years ago
|
||
Solitude was migrated last week. When would you all like python 2.7 enabled on zamboni dev?
Comment 19•11 years ago
|
||
Would it make sense to switch over webpay first?
Comment 20•11 years ago
|
||
Works for me.
Reporter | ||
Comment 21•11 years ago
|
||
Don't see why it should block on webpay.
Comment 22•11 years ago
|
||
I guess it doesn't matter, but I figure it'd probably be best to make sure nothing explodes on the smaller projects first. If something on webpay breaks, it'd conceivably be easier to mop up the damage and prepare zamboni than it would be to mop up the damage if we dove into zamboni first.
Reporter | ||
Comment 23•11 years ago
|
||
All the tests for webpay are on 2.7 and so is -dev. All we've got to do is prod and stage, which given the schedule makes sense to do in the new year. But I don't anticipate any issues at all.
Comment 24•10 years ago
|
||
When would you like me to upgrade stage?
Comment 25•10 years ago
|
||
Today is good, let's let QA finish up with what they are doing right now. Will give the high sign on IRC
Comment 26•10 years ago
|
||
(In reply to Wil Clouser [:clouserw] from comment #25) > Today is good, let's let QA finish up with what they are doing right now. > Will give the high sign on IRC My mistake. Sounds like the next step for this would be to get jenkins running 2.7 so we can make sure the tests pass. I think that's on us.
Comment 27•10 years ago
|
||
Did jenkins tests ever get switched to 2.7?
Updated•10 years ago
|
Priority: -- → P4
Updated•10 years ago
|
Flags: needinfo?(clouserw)
Comment 28•10 years ago
|
||
I don't think I have access to tell you. Jason is the jenkins-master, right?
Flags: needinfo?(clouserw)
Assignee | ||
Comment 29•10 years ago
|
||
To have the AMO jenkins test use python27 we just need to add the following lines to build scripts https://github.com/mozilla/solitude/blob/master/bin/jenkins.sh#L5-L7 and wipe the current workspace.
Comment 30•10 years ago
|
||
clouserw, is anyone assigned to the python27 migration? Looks like the next step is mentioned in comment #29.
Flags: needinfo?(clouserw)
Comment 31•10 years ago
|
||
(In reply to Jeremy Orem [:oremj] from comment #30) > clouserw, is anyone assigned to the python27 migration? Looks like the next > step is mentioned in comment #29. No, but that's a good summary - thanks Jason. It will become part of Marketplace's repoman strategy (a rotating team working on debt/maintenance). I can file bugs for the projects. Jason - how do we "wipe the current workspace" ?
Flags: needinfo?(clouserw)
Comment 32•10 years ago
|
||
Just wanted to note that the first redhat release candidate was announced today. If we want to wait, we won't have to deal with the SCL stuff.
Reporter | ||
Comment 33•10 years ago
|
||
(In reply to Wil Clouser [:clouserw] from comment #31) > (In reply to Jeremy Orem [:oremj] from comment #30) > > clouserw, is anyone assigned to the python27 migration? Looks like the next > > step is mentioned in comment #29. > > No, but that's a good summary - thanks Jason. > > It will become part of Marketplace's repoman strategy (a rotating team > working on debt/maintenance). I can file bugs for the projects. Jason - > how do we "wipe the current workspace" ? I can do this step, I've done it for webpay and solitude, my only concern is that I don't want to have jenkins and prod diverge for too long. I'd rather set up a seperate marketplace-27 build in jenkins and run the two in parallel. It increases the jenkins load, but *shrug*.
Assignee: oremj → amckay
Reporter | ||
Comment 34•10 years ago
|
||
https://ci-addons.allizom.org/job/marketplace-python-27/ There was a git recursion error and an ES error. But no Python error. Woot. When Python 27 is good to go, we can remove the old builder (or this one or whatever). It's currently on manual builds to avoid ES conflict. Pinging Allen, with the tests (almost) passing are there any code changes you think we should make, or just go for it?
Comment 35•10 years ago
|
||
Everything should work on 2.7 with no changes so far as I know -- I've been using 2.7 since the beginning of the year locally.
Flags: needinfo?(ashort)
Updated•10 years ago
|
Priority: P4 → P3
Updated•10 years ago
|
Summary: Move zamboni to Python 2.7 → [mkt] Move zamboni to Python 2.7
Updated•10 years ago
|
Component: Server Operations: AMO Operations → Operations: Marketplace
Product: mozilla.org → Mozilla Services
Version: other → unspecified
Reporter | ||
Comment 36•10 years ago
|
||
Jenkins is using 2.7 now I believe, can we upgrade our servers some time soon?
Assignee | ||
Updated•10 years ago
|
Whiteboard: clouserw=p6
Reporter | ||
Comment 37•10 years ago
|
||
Django 1.7 has been released today and drops Python 2.6 support. So would be good to move to 2.7 soon.
Assignee | ||
Updated•10 years ago
|
Assignee: oremj → jthomas
Reporter | ||
Comment 38•10 years ago
|
||
Bump?
Assignee | ||
Comment 39•9 years ago
|
||
Done on dev, stage and prod.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•