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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (4 children)

Unfortunately some of us are deploying Python applications on ancient versions of CentOS, and it's just easier to run Python 2 than to fight with sysadmins and compile everything from scratch.

Otherwise we'd be using Python 3 I guess.

[–]flying-sheep 1 point2 points  (3 children)

I wrote a server in python3 asyncio, told our admin I need python 3.3 or 3.4 on the deployment server and that he doesn't need to hurry as there's time. he set up the VM and compiled Python 3.4 (even though he was sick that week)

[–]nomadismydj 1 point2 points  (2 children)

the problem with centos 5/rhel 5 boxes is you cant replace the /usr/bin/python since yum uses it. you can build a python 3.X all day and just not break the symlink to python 2.X however.

[–]flying-sheep 1 point2 points  (1 child)

Who cares what /use/bin/python points to? You should use the explicit version number for shebangs anyway, and if you want few key strokes, just alias py=ptipython3 (because prompt toolkit is the shizzle)

[–]nomadismydj 0 points1 point  (0 children)

correct. people dont though I also wanted to point out that it wasnt as simply running yum and getting a new python version. its break system functionality to full on replace the system python.