{
  "video_id": "reddit_1tqgaw9",
  "channel_slug": "programming",
  "channel_handle": "r/programming",
  "title": "Some Python Features We Almost Got but Never Did",
  "url": "https://www.reddit.com/r/programming/comments/1tqgaw9/some_python_features_we_almost_got_but_never_did/",
  "external_url": "https://medium.com/techtofreedom/9-python-features-we-almost-got-but-never-did-4fcc5b358d55?sk=109955a1b32136b807cedbf1ab46b193",
  "upload_date": "20260528",
  "published_at": "2026-05-28T20:59:14+00:00",
  "transcript": "\n\n--- Top Comments ---\n\n\n[75 upvotes] > The hard part is not only parsing the code. The hard part is deciding whether the extra compactness makes Python easier to read. Optional chaining can be beautiful in small doses:\n> \n>     name = user?.profile?.display_name ?? \"anonymous\"\n> \n> It can also become a fog machine:\n> \n>     value = request?.user?.team?.billing?.plan?.limits?[\"exports\"] ?? 0\n>\n> At some point, the shorter expression may hide the fact that the program does not really know which object is allowed to be missing.\n\nOK, we clearly have different opinions about what makes code clear because to me that second one is basically the perfect way to express that code. It's certainly better than writing out 7 if statements\n\nYes, if you have this many optional values to deal with you probably need to restrict your types better but that's not the fault of the null-handling operators\n\nEdit: After reading further I'm pretty sure this is just written by AI\n\n[8 upvotes] The fact that PEP505 hasn't been accepted is legitimately insane. Many other languages have this feature already. ",
  "transcript_chars": 1096,
  "ingested_at": "2026-05-29T01:30:45.519782+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 65,
    "upvote_ratio": 0.81,
    "num_comments": 14,
    "author": "yangzhou1993",
    "is_self": false
  }
}