[sago]

I like to remind people that Python 3 was already more than a year old when Apple announced the first iPad. I'm not sure anyone should be getting a cookie for 'working on' Py3 support more than nine years later. Though I do understand that GAE has supported Py 3 for a while in its more configurable service.

[raverbashing]

True, though I have to say it only got usable around 3.4 (which still is 4y.o. at this point)

[sago]

What did 3.4 give you that 2.7 already had? I have found bundled pip and asyncio useful, but I was using Py3 from 3.2, successfully. It didn't suddenly become usable at 3.4 for me.

[toyg]

I think what happened was that 3.2 was the first "real" release, when a lot of .0 bugs were shaken out; the 'u' prefix was added back around that time too, iirc.

This resulted in more developers actually porting their libraries, an effort that had been basically non-existent before. The result was that the 3.4 ecosystem actually got mature enough that Real Work could get done, and more end-users started moving.

IIRC 3.3 also had some big performance problems that were sorted in 3.4, but I cannot remember the details.

Personally, I did very little with 3.2 but actually built Real Stuff only with 3.4.

[raverbashing]

Yeah, pip. You could install it manually, but to be honest, pip and virtualenv are fundamental today (I mean, before containers, but still)