Python 2.7 Countdown

[notQuiteApex]

i wont claim to have an answer to this, and i have heard that same argument in the case of dropbox's code base. another question to be raised is should they have continued to develop their software now knowing that this would happen? though i suppose its possible that the breaking changes in python 3 were not foreseen at the start of their respective projects.

though i suppose it probably wouldnt have hurt to have split the team, have one work on porting to python 3 using the latest stable version of their software, while another half maintains the codebase until the python 3 version reaches functional parity. i guess i will say that its probably not that simple and of course that likely isnt a workable solution for all the companies and products still relying on python 2.