David Zaslavsky on Nostr: npub172v3n…u689n Nah I didn't mean to request a blog post (I'm not the type to make ...

npub172v3nlrtzd8wssn8f3ckm47jtsxdhq0jakqua3crgrvn7mmv32vsju689n (npub172v…689n) Nah I didn't mean to request a blog post (I'm not the type to make such a request so obliquely), but if you did feel like writing one it might help clear up some things. Like, when you say not to use namedtuples in new APIs, is that your opinion or are you representing some kind of official position (which is what I thought you meant)? Or, if it's not official, is it an opinion widely shared among core devs, such that usage of namedtuples might be deemphasized if not actually deprecated in the future? In which circumstances are namedtuples appropriate? And ultimately the important thing is probably, why are namedtuples otherwise undesirable and what would you suggest people use in cases where they're not appropriate? Like, would this new proposal you have be a suitable namedtuple replacement, or would you suggest dataclasses in some cases, or something else?

No obligation of course, I'm just trying to represent my perspective of what information I'd find useful.