> have a 3.5 that has print statement Yeah, because THAT is clearly what's blocking Python 3 adoption, with "from __future__ import print_function" being there

> have a 3.5 that has print statement Yeah, because THAT is clearly what's blocking Python 3 adoption, with "from __future__ import print_function" being there since 2.6. It seems almost insulting that after years of relative stalling, now that Python 3 is really taking off (Django, Numpy ...) some people feel suddenly lazy about it.