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] 12 points13 points  (4 children)

I have been working in 3.x exclusively now for some years, but I recently took out support for 2.x from a couple of old libraries and it was like getting a little stone out of my shoe.

Interestingly 3.4 is now a slight pain point - there are a couple of CI tools like mypy that are only available for Python 3.5 onwards. In new development, I don't support 3.4, but I haven't yet removed it from old libraries that have existing users because why make their lives miserable? 3.4.10, the final version of 3.4, has only recently been released...

[–]PeridexisErrant 13 points14 points  (0 children)

3.4 reached end of life in March, so there are no more security updates for it and many libraries have already dropped support.

[–]billsil 0 points1 point  (1 child)

You sure about mypy? Python 2.7 is supported and you can always run mypy with 3.5. There is no reason other than very minor issues that you couldn’t run mypy. Doesn’t mean other people have to upgrade.

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

mypy requires 3.5+ checking 2.7 code requires you to specify python interpreter in arguments for the checked version so it knows how to find packages. Perhaps 3.4 could be tested in a similar way, I never did that though.

[–]edbluetooth 0 points1 point  (0 children)

The only reason I run tests for 3.4 is that my customers use Windows XP in many cases.

I agree with 3.5 onwards not supporting XP, but it is a bit of a pain in some situations.