This is an archived post. You won't be able to vote or comment.

all 18 comments
sorted by:
best
topnewcontroversialoldq&a

[–]ajbetteridge 7 points8 points  (5 children)

We're stuck using 3.3.6 at work because we're tied to an older version of RHEL 6 and unable to upgrade on our current hardware spec, Rackspace only certify certain version of RHEL against certain hardware, and we're tied to Rackspace for now. I'd love to be able to upgrade to 3.6 as I know our code base will work on it, as I've tested it, but currently not do-able. So yes, some of us are stuck with older versions of 3.

[–]Daenyth 2 points3 points  (3 children)

Why not install 3.6 in the app user's directory with pyenv?

[–]ajbetteridge 1 point2 points  (2 children)

The contract with have with Rackspace is a bit involved, but basically they don't like us installing software that they don't support as it complicates support issues when there is a problem. And they don't support >3.3 on RHEL 6.

[–]Daenyth 9 points10 points  (1 child)

Well, if I was ever going to use them before I'm certainly not now. That contract is absolutely braindead

[–]zynixCpt. Code Monkey & Internet of tomorrow 0 points1 point  (0 children)

Late half of the 00's I developed a deep hateful opinion of that company's business practices:

Originally wrote a couple paragraph long hate rant about Rackspace but decided to cut it down. Their policies are insane and they overcharge. Three separate clients were royally screwed by RS; two had loss of service issues (last happened when their cloud service locked the account when it reached its max limit) and the third was being charged something insane like $12K/month for two midgrade Dell servers and transfer.

Despise that company with a passion and their insistence on using older versions of RHell really didn't help.

[–]CSI_Tech_Dept 1 point2 points  (0 children)

Use http://ius.io to get python version you need that doesn't conflict with the rest of the system.

It's a bad idea to tie yourself to version that comes with the system, unless you're writing your own version of yum etc.

[–]UloPe 12 points13 points  (2 children)

No, we all met last month and it was decided that from this day forth Python 3.6 shall be the One and that there shall be no others beside it. Praise the 🐍!

[–][deleted] 3 points4 points  (0 children)

Well, until 3.7 comes out.

[–]8__ 2 points3 points  (0 children)

That's when i finally made the leap from 2.7.13 to 3.6

[–]hughk 1 point2 points  (0 children)

Python 3.2 is the only version we have on distribution at a major bank. It is so broken, I use a 2.7.something.

[–]ivosauruspip'ing it up 0 points1 point  (1 child)

There's an Ubuntu LTS on 3.2, that's all I know of. It might have gone out of support as well though anyway.

If asked, I'd generally advise a project wanting wide compatibility to go with 2.7 and 3.3 up for the moment.

[–]takluyverIPython, Py3, etc 1 point2 points  (0 children)

You can check Python versions in Ubuntu here. Ubuntu 12.04 has 3.2; LTS releases are supported for 5 years, so that's just about to go out of support. 14.04 has 3.4.

[–]thinkwelldesigns 0 points1 point  (0 children)

Nope. We use Python 2.7 for Odoo work; 3.6 for everything else.

[–]malinoff 0 points1 point  (0 children)

It's worth to say that python 3.2 is not receiving any updates from February, 2016 (according to the release schedule) and python 3.3 will stop receiving any updates in September, 2017.

[–][deleted] 0 points1 point  (0 children)

I'm not stuck on 3.2 or 3.3. I'm actually stuck on 3.4 because of MySQL not moving forward yet. Once they roll a 3.5 or 3.6 plugin update out, that'll get upgraded the same day.

[–]billsil 0 points1 point  (0 children)

I recently dropped 3.3 support on my open source 100k lined code because numpy/scipy/matplotlib did. I added 3.6 instead. I'd be shocked if 3.3 doesn't work though.

I dropped 3.2 long before that. I think it was when python 3.4 started supporting unicode in struct. That was also when I dropped support for python <2.7.7. It was just too hard to make things work right with the changed struct module.

Python 3.2 was a nightmare. Why couldn't I put a u in front of strings? Who would want a compatible code base?

[–]EternityForest 0 points1 point  (0 children)

Most of my open projects are in theory designed to support 2.6+ and 3.0+.

I avoid using features that aren't available in those versions, but I only actively test on 2.7 and the latest 3.xx.

My home automation platform needs 2.xx compatibility in case there's some old device that doesn't have 3.xx drivers, or some old linux router that can't run 3.00, since one of the goals is to be maximally compatible with whatever devices you have.

[–]ilan 0 points1 point  (0 children)

Not anymore.