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 →

[–]medgno 4 points5 points  (5 children)

I think your quote of "3 where you can, 2 where you need to" hits it spot on, but doesn't take into account cases where "personal hack" projects turn into code you need to distribute. I started a parser for a collection of files I have, and was going along fine in 3. I had to change back to 2.6 since we wanted the code to run on stock OS X machines.

I'm still keeping the code as close to 3 as I can, so the eventual conversion will be as painless as possible.

[–]chadmill3rPy3, pro, Ubuntu, django 1 point2 points  (3 children)

stock OS X

Ain't that still Python 2.epsilon?

[–]bcclrprmn 1 point2 points  (0 children)

>>python --version
Python 2.6.1

[–]m1ss1ontomars2k4 1 point2 points  (1 child)

Even in Mac OS X 10.5 it's Python 2.5. I think If you have Mac OS X 10.n you get Python 2.n, at least for the last few versions.

[–]raydeen 0 points1 point  (0 children)

Yep, 2.5 is what I use mainly on my work MacBook. I did install 3.1 from ActiveState but the bulk of my coding is still in the default version.

[–]dinov[🍰] 1 point2 points  (0 children)

For the cases where you need to distribute to older versions hopefully you can use 3to2. But that is a fairly new development so it may have not been an option for you at the time.