3 ms·
> E: py3 was released in Dec 2008. So I guess those first two years might have been tough. 3.2 was released early 2011, and P2 compatibility features were rein
by masklinn 5y ago
> E: py3 was released in Dec 2008. So I guess those first two years might have been tough.
3.2 was released early 2011, and P2 compatibility features were reintroduced as late as 3.5 (% on bytes) in 2015, though for my money the last key one was the reintroduction of the `u` prefix in Python 3.3, in 2012. That's the point at which the migration really became feasible without suffering.
Furthermore that's assuming all dependencies were ported, which was not the case: waiting until porting was feasible (and they had the time and manpower to) was also something they had to wait on e.g. Django first added Python 3 support in 2013 (IIRC PyLint only supported 3.4 onwards), difficult to port your own software if the stuff you depend on hasn't been ported over.