Made with KolourPaint and screenshots from Kate (with the GitHub theme).

    • _stranger_@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      2 days ago

      Dude, even just a “FY,I, you sure about this?” would be nice. I gladly embrace python’s by-all-means-shotgun-your-leg-off philosophy, but the noobs could use the help.

      • lime!@feddit.nu
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 hours ago

        the problem is that the language doesn’t and can’t support one single way to use type annotations without changing fundamental functionality. you can absolutely hook up mypy to your editor for newbies, but once you get on the intermediate level, fighting with mypy takes more code than actually solving the problem.

        also there was that proposed update to mypy that was put on held when it turned out that the maintainers didn’t know how annotations are used in the wild.

        • _stranger_@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          4 hours ago

          Oh I’m well aware. Took me a solid year to appreciate type annotations for what they are and yeah I’m happy using what we have in stdlib now and not messing with mypy tyvm. The problem is that history is lost to newcomers who have very different expectations. Modern IDE’s mostly solve it though, so for all my Java peeps dipping their toes into the snake waters, listen to your ide

          • lime!@feddit.nu
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 hours ago

            i mean, i’m all for rejiggering the internals. i’ve personally written at least two libraries that uses type annotations in reverse to force arguments into the correct type, and i feel like that should probably be a separate mechanism to “just call the annotation”