Porting from py2 to py3 is a "lot" of work and has a lot of risk. See (was it?) Instagrams keynote at PyCon of how one missing "b" prefix cost them 10% or so p

Porting from py2 to py3 is a "lot" of work and has a lot of risk. See (was it?) Instagrams keynote at PyCon of how one missing "b" prefix cost them 10% or so percent of runtime performance (can't remember the exact number). For every project that ports, the risk goes down for the rest (of those who still need to move), as more bugs are uncovered and more lessons/best-practices have been learned. Hence porting late is an advantage from a cost/risk point.. Also, if there are no strong technical people advocating for the change, most organisation only see porting as a (unnecessary) costly exercise.. I think the judge is still out on whether that is really disproved, but right now you are likely correct :)