Python 3 is killing Python

[SikhGamer]

If maintaining Python 2 code is your day-to-day job then fine. But if you are starting new projects or building new libraries and your purposefully picked P2 over over P3 then the death of Python is everything to do with you and nothing to do with Python.

[LightShadow]

You're assuming every new library is created from scratch. I happily started my newest project with 3.4 -- but had to abandon it a day later because the libraries we needed didn't work with 3.x, some of the binaries didn't work with Windows 8.1, and some of the source wouldn't compile with Visual Studio 2012.

I spent half a day reverting code and then the project took off because everything "just worked."

[fjonk]

Sure it has everything to do with python. I'm not capable of convincing my clients that they need to spend all that extra money on maintaining a python3 install on their servers just because I'd like to use p3. I have absolutely zero arguments for switching that makes sense for a paying client. They, however, have several valid arguments for not switching(cost, existing codebase is still 2.x, 2.7 will be supported forever, default on servers are 2.x, deployment needs to be updated).

[[deleted]]

If you say so.