• FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    29
    ·
    15 days ago

    To be fair this was quite wtf-free. Mostly just unimportant formatting subtleties and stuff you’d never write.

    Python definitely has bigger WTFs, like bool being an int, implicit bool conversion, implicit iteration of strings, etc.

  • sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    15 days ago

    Hmm: 17/26

    Failures were:

    • didn’t know about the = option, but once I saw it once, I guessed right a few times
    • never used ^ in Python, and didn’t make the connection to XOR (I figured I’d need the math library or something)
    • the r and a with =! (again, never used = option)
    • edge cases in walrus operator and other things unrelated to f-strings

    Most of those I missed (and many I got) I’d reject a PR over because it’s not obvious enough what’s going on. But I think given that, I did reasonably well.

    But I learned something. Thanks for the post!

  • spacemanspiffy@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    ·
    15 days ago

    This is fun, as was the JS date one. I hope people do more.

    Still though, I don’t think doing well or not on these necessarily mean you’re good or bad with the language.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      arrow-up
      12
      ·
      15 days ago

      I love the walrus operator:

      if (x := some_function()):
          do_something(x)
      else:
          # x is None or False or something, consider it invalid
      

      The only thing I wish was different is adding a scope, which would make x invalid outside the block. But Python’s scoping rules are too dumb to handle this case.

      • Ephera@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        15 days ago

        In lots of functional languages, you’d have some_function() return an Option type and then you’d use .map() or similar on it to only do something when the value is defined. I think, that can be done in Python’s syntax, but you need a library for the Option type…

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          arrow-up
          3
          ·
          15 days ago

          Python has an “Optional” type, but it’s merely an alias for T | None. I wish Python had better support for FP, but each time it gets close, it doesn’t quite go far enough.

          For example, it now has match blocks, but there’s no error if the match is exhaustive, which hurts formal proofs of correctness. Likewise, tons of other features fall a bit short, but in general it’s workable with some discipline.

      • 🇨🇦 tunetardis@piefed.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        15 days ago

        I think my most common use case is with dictionary lookups.

        if (val := dct.get(key)) is not None:
            # do something with val
        

        I’ve also found some cases where the walrus is useful in something like a list comprehension. I suppose expanding on the above example, you you make one that looks up several keys in a dict and gives you their corresponding values where available.

        vals =  [val for key in (key1, key2, key3) if (val := dct.get(key)) is not None]
        
    • kryptonianCodeMonkey@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      15 days ago

      Walrus operator does an inline assignment to a variable and resolves to the value assigned. If it is in a condition statement, like “if x := y:”, it assigns the value of y to x then interprets the expression of the condition as of it just said “if x:”. Functionally, that means the assignment happens regardless of the value of y, but the condition only passes if the value of y is “truthy”, i.e. if it’s not None, an empty collection, numerically equal to zero, or just False.

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    8
    ·
    15 days ago

    Your final score: 9/26

    There were more nuances and surprised than anticipated. But it should be expected, because its on this website. :D But any language with duck typing and lot of magic and interpretation, and a long history of changes and additions, used in a huge variety of environments, is bound to be surprising. I am not surprised that JavaScript and Python are surprising.

    • logging_strict@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      15 days ago

      What to know about f strings

      !r is a thing

      !s is a thing

      There is some syntax for formatting a float which will completely be forgotten that’ll have to be looked up.

      There is nothing else worth knowing.

      Now lets moan and complain about something actually important. Like repos with languishing PRs, like SQLModel.

  • salmoura@lemmy.eco.br
    link
    fedilink
    arrow-up
    5
    ·
    15 days ago
    Tap for spoilers

    I was sure something was wrong with the first question, probably because of the linter in my editor.

    TIL about the feature in #4, it’ll be handy in my day-to-day businesses.

    I forgot about the escaping in #7.

    #19: what?

    From then on, it was all [uneducated] guesses.

    12/26, need more practice.