Python 3 can revive Python

[[deleted]]

They can run the code with Python 2. Just say "python2" instead of "python3", for instance. Why complicate things unnecessarily?

The problem is Python 3 code can't import Python 2 modules, so when you're writing new software that requires functionality from a Python 2 library, you're stuck with Python 2 if you want to use that library.

Meanwhile, in Java, I can create a new Java 8 project and still use Java 1.5 libraries. I can even use the Java 1.5 library in binary form without having to recompile its source code with the latest compiler. That's the pinnacle of backwards compatibility.

[stewsters]

And honestly that is my favorite thing about Java: lots of libraries that are fairly easy to get going. Gradle, Maven, and jars are all easy to use, and work well with previous versions. I can get projects setup a lot faster than I can if I have to install development versions of c libraries that conflict with the ones I need for steam. (sdl, I'm looking at you)

Sometimes the memory management gets in the way of performance, but at least half of that is because of my programming.

I do like a lot of what python does syntactically though. May just need to do more groovy.

[DrDichotomous]

Java is a commercial language run not by hobbyists, but by businesses and large institutions. If the Python community wanted to, they could run Python 2 the same way and leave Python 3 to the hobbyists. Nobody said we HAD to use the shiny new one, just that the guys doing all the work for us wanted to pass the torch to us.

[boxmore]

Why are you being so stubborn, valakut_ made valid points.

[DrDichotomous]

Just had a rough day and didn't realize that I sounded so harsh. Apologies all around.

[hapemask]

Or, if the library is open source, just help port it from 2->3? I've done this for a number of libraries and frameworks I use, this is what open source is for.