> meh, there isn't (still) any reason to really jump onboard python 3, 2.7 is good enough for me You're siding with a shrinking ecosystem (Python 2) over a gro

> meh, there isn't (still) any reason to really jump onboard python 3, 2.7 is good enough for me You're siding with a shrinking ecosystem (Python 2) over a growing ecosystem. Depending on your use case, this could range from inconsequential to inconvenient to disastrous. If you have an existing codebase in Python 2, then perhaps the conversion to 3 isn't worth the effort. But if you're developing new software, the question is why not make the minimal investment to make your work compatible with the future of the language? When I see a new library and the author couldn't be bothered to adopt Python 3, it's a big red flag.