• AVincentInSpace@pawb.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    18 hours ago

    For the last time, Python is not weakly typed. It is dynamically typed. The statement 5 + "hello" results in a type error. Bash is weakly typed, and that same addition results in 5hello

    • NaevaTheRat [she/her]@vegantheoryclub.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      16 hours ago

      Why do people think Python is ducktyped? The syntax is quite explicit, just because x = 5. is shorthand for x = float(5) doesn’t mean it’s doing weird mutations. The closest would be maybe that something like:

      x = 5
      y = 2.
      z = x * y
      

      works (I think) but that’s not exactly a wacky behaviour. It’s not like it ever does the wrong behaviour of casting a float to an int which can erase meaningful data and cause unpredictable behaviour.

      I mean you can (and often should!) give functions/methods type signatures ffs.

      • AVincentInSpace@pawb.social
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        16 hours ago

        Because to a certain extent Python is duck typed. Python has no concept of interfaces, unless you count the abc module combined with manual isinstance() checks, which I’ve never seen anyone do in production. In order to be passed to some function that expects a “file-like object”, it just has to have methods named read(), seek(), and possibly isatty(). The Python philosophy, at least as I see it, is “as long as it has methods named walk() and quack(), it’s close enough to a duck for me to treat it as one”.

        Duck typing is distinct from weak type systems, though.