You can add a lot of bugs that wouldn't be obvious with the port. It took me two weeks to port a somewhat large codebase, and there were some bugs in it for a good month that we caught over time. For a larger codebase it could be such a pain in the ass.
But really, why is it worth the effort if the 2.7 version works as intended? I don't think this is so much "why not" as much as "why". Unless you know a python 3 lib that you really want or some library you use has a lot of bugs fixed and stopped supporting 2.7, there's not much point other than to say you have a modern codebase. A lot of people still know 2.7 and people who learned starting at 3 can pretty easily work with 2.7 without breaking a sweat.
Starting a new project in 2.7 wouldn't make much sense, but supporting an existing codebase using 2.7 can make more sense than porting it.
But really, why is it worth the effort if the 2.7 version works as intended?
Is no programmer familiar with the concept of technical debt anymore?
Technical debt... is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.
Technical debt can be compared to monetary debt. If technical debt is not repaid, it can accumulate 'interest', making it harder to implement changes later on. Unaddressed technical debt increases software entropy.
. A lot of people still know 2.7 and people who learned starting at 3 can pretty easily work with 2.7 without breaking a sweat.
You don't understand... there will soon be no more 2.7 support. Major libraries are already ending 2.7 support ahead of schedule. Want the newest version of a web framework, of Pandas, etc.? Sorry, they've already said there will be no more versions for 2.7. Want to take advantage of a new OS feature? Sorry, libraries won't be updated anymore. A bug in Python? Sorry, no one's going to fix it. Then like the people who kept using Windows XP, you're going to find your hardware or Windows 23 won't run Python 2.7 anymore and you'll scream and cry and wail "But I never had time to port it!!!" You had 73 years; you just didn't bother. You kept writing more and more 2.7 code, making the eventual INEVITABLE porting even harder.
0
u/[deleted] Jul 29 '18
[deleted]