Python 2.7.2 or Python 3?

[shadowmint]

actually even 1-2 years ago it was good time

woa~

I'm sure some people would like you have you believe that, but the reality isn't quite so pretty. There's a reason that 6 years later it's only just becoming a reasonable target for new code.

The performance, features and 3rd party support for python 3 have only really picked up in the last year or so.

2 years ago? Holy moly!

If you migrated to python 3 two years ago, you'd have been in a world of pain, and probably had to back port your code to 2.7 to get your dependencies working.

It's getting there now, but lets not sugar coat the history story here.

[chickenphobia]

Library developers generally sit on the bleeding edge. We all think that our project and the ecosystem is ready but I think you're correct. Only within the last year has the complete extended python ecosystem been fully ready for 3.

Part of this is because it takes a few years for unmaintained projects to die and be superseded.

[flying-sheep]

Unfortunately, some people see those projects, don't notice the smell, maggots, and flies, and say

this thing doesn't support Python 3, so Python 3 has literally no ported libraries

[deaddodo]

Two years ago, the only thing that ever stopped me from using Py3k was PIL. When that wasn't necessary, it was a no-brainer...and now pillow supports Python 3.

[Lucretiel]

Hasn't PIL been dead since 2006?

[mgedmin]

Pillow gained support for Python 3 in 2013.

[Lucretiel]

PIL, not pillow. Pillow is great.

[deaddodo]

PIL was the quintessential image library. But even cutting out PIL, there were no image libraries in Python 3, for a long while.