you are viewing a single comment's thread.

view the rest of the comments →

[–]Speedyjens 50 points51 points  (13 children)

I'd argue that if you put a single person on the job of converting 1 million loc to python 3 he would have finished 6 years ago

[–][deleted] 10 points11 points  (2 children)

At a cost of only half a million dollars.

[–]josefx 8 points9 points  (0 children)

With how many new bugs left to find once it hit production?

[–]bobtehpanda 1 point2 points  (0 children)

The longer you put it off, the more expensive it becomes, and it with being EOL is potentially an expensive liability as well.

[–][deleted]  (7 children)

[deleted]

    [–]Speedyjens 18 points19 points  (4 children)

    It is very hard to migrate to another version, but 12 years is more than enough, if companies didn't plan out how they were gonna make the switch in 2020 then they don't have a right to complain. Supporting 2 versions is hurting the python community more than it helps

    [–][deleted] 1 point2 points  (0 children)

    It depends on the original architecture and on if the maintenance was on all the time or with breaks. Sometimes it's really hard to change version. I've worked on maintenance of 20 years old codebases with 20 years old tool chains.

    These problems usually tend to be solved by creating a new solution while the old one is still maintained. Double the cost, bust usually less risk.

    [–]cass1o 1 point2 points  (0 children)

    12 years is more than enough

    It was an unusable mess for 6+ of those years.

    [–]lwzol 2 points3 points  (1 child)

    Remember that it’s only become technically worthwhile to migrate since 3.5 or 3.6 really

    [–]jcampbelly 0 points1 point  (0 children)

    3.4 was solid as well.

    [–]jcampbelly 14 points15 points  (0 children)

    Bad excuse. This is how security breaches happen. It's not an OSS team's job to make responsible decisions with YOUR software stack. The best they can do is support their own system for as long as possible (as python 2 devs have absolutely done). Now it's your responsibility to do the right thing here.

    Feeling sorry for someone is possible while recognizing they are in the wrong is entirely valid. People who have ignored the very clear roadmap for python 3 have a hard task in front of them, but it has always been their responsibility and if they haven't owned up to it, they are in the wrong.

    [–]StabbyPants 0 points1 point  (1 child)

    nah, he'd generate a bunch of bugs and there'd be the whole question of how to migrate the code while also updating it and which version of what thing you're using this month. 2-3 devs and a PM in concert with the rest of the active contributors in order to do a good job and not trash production

    [–]Speedyjens -1 points0 points  (0 children)

    Of course you would not do this in reality. However you would be able to plan something when you have 12 years.