3 ms·

I used it production just fine before that. What didn't work for you? The unicode support was shoddy, but lots of other stuff worked fine. The problem as I rem

I used it production just fine before that. What didn't work for you? The unicode support was shoddy, but lots of other stuff worked fine. The problem as I remember it was that there were some critical tools that just were not making the switch. The last one I could remember having to have a separate runtime for was graph-tool, but there were just a ton of them in the scientific computing community. Also, I don't think making print a function was worth it. So many people had muscle memory on that that personally I think it was worth just single casing it.

loudthing 5y ago
Alex3917 5y ago
> What didn't work for you? Weren't there a lot of major performance regressions in the first couple versions?
- paganel 5y ago
  There definitely were, at least in the early versions. It would have been fine (I guess) if those early versions/iterations had been short-lived, so to speak, and for a stable and definitely faster version (compared to 2.7) to be made available shortly after that, but afaik that wasn't the case. If it matters I've been writing Python professionally for more than 15 years and I started my career by seeing the (less famous) Zope2 to Zope3 botched migration. When Python3 was first announced I had hoped that the devs behind the project had learned from that related experience, guess I was wrong.