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

Python

6356 readers
10 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
8
Proposing a struct syntax for Python (snarky.ca)
submitted 1 year ago by jnovinger@programming.dev to c/python@programming.dev
8 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
[โ€“] erez@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

I agree with the article that dataclasses and namedtuples aren't as good as they can be. But I think the solution should be to make dataclasses native, and not namedtuples.

So we could write something like:

dataclass Point:
  x: int   @"why not also add new syntax for documentation?"
  y: int   @"the size of translation on the Y axis"

  def methods_as_usual(self):
      ...