• Overarch3784@kbin.social
    link
    fedilink
    arrow-up
    25
    ·
    1 year ago

    I think the biggest problem would be libraries which are not available in 3.x. I just rewrote a python script some time ago and the syntax changes were pretty easy to change with search and replace.

    • Dr Cog@mander.xyz
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      I don’t see a problem. For one, it’s been 15 years: the vast majority of libraries have been ported by now. And like you said, you can fix the syntax with basically a find/replace script, so any stragglers can be modified easily.

      There really isn’t any excuse to still be using Python 2 anymore

      • Alphare@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        While I agree that people should have moved on for a while, the idea that porting Python 2 to 3 only involves “find and replace” or a tool like 2to3 is only true in the most trivial cases. Anything that touches bytes, unicode, network or files to do anything remotely involved needs a lot more care. I should know, our codebase still suffers from the occasional bug due to this, even though it’s been years.