Story time When I go on vacation with a fellow Python developer, inevitably I will talk about Python. 😁 Back in September, Andrea and I drove the Cabot Trail with our friends Dusty and Jen, which led to a discussion about the match statement and how Dusty and I both wished

I’m still digesting this one and haven’t formed any strong opinions yet.

I’ve had problems in the past where this could have been useful, like ingesting millions of lat/long positions and trying to string them together in a “trail”. But, I was still able to handle that fine with namedtuple without too much pain.

Thoughts?

  • DanCardin@programming.dev
    2·
    1 year ago

    I wouldnt hate its existence, and certainly i would always prefer anyone use this over namedtuple.

    At the same time, i think i would never use it. 90% of my classes these days are dataclasses, and the set that don’t inherit from anything, and have no methods are vanishingly small

    I don’t know that harkening to rust structs makes much sense in python, (…which can have methods)