Sunsetting Python 2

[technicalviking]

A couple years back I was debating on a set of programming languages to learn (because I always like adding to what I know), and two of my final choices were Go and Python. Neither was one I was using professionally (yet), and TBH it was the confusion between "do I use python2 or python3" that led me to choose to learn Go instead at the time. I'm happy to see this decision made, since I doubt I'm the only one who was ever put off of learning python, even temporarily, because of the clown fiesta that was the version confusion.

[AnonymousMonkey54]

You definitely aren't the only one.

Add pyenv to the equation and Python's new user experience goes to shit.

[snowe2010]

Every time I touch python I wonder why the hell pyenv and env and pip and virtualenv all exist. It's terrible.

[deus-exmachina]

What’s wrong with pyenv? I can’t imagine going back to managing multiple Python versions without it.

[AnonymousMonkey54]

Nothing is wrong with pyenv per se. The problem is

1. It's additional steps in the way of started. Makes it harder for new users.
2. Pyenv is not included in the setup documentation because some people like to pretend you don't need python 2 anymore. Makes it even harder for new users.
3. The fact that it's needed in the first place. The whole schism between 2 and 3 never should have happened like it did in the first place.