this post was submitted on 14 Jun 2023
4 points (100.0% liked)

Python

6281 readers
85 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

๐Ÿ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

๐Ÿ Python project:
๐Ÿ’“ Python Community:
โœจ Python Ecosystem:
๐ŸŒŒ Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
4
Proposing a struct syntax for Python (snarky.ca)
submitted 1 year ago by jnovinger@programming.dev to c/python@programming.dev
7 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] NullNowhere@lemmy.dbzer0.com 4 points 1 year ago

Opinion: This doesn't really solve a problem like dataclasses v. namedtuples did. This mostly boils down to someone not really liking the dataclass syntax and deciding that adding yet another way to write classes is the way to go and is somehow more teachable (because now we need to teach both).

Maybe it'd be nicer in a few use cases, but I don't really feel it's worth the expansion to the syntax burden.