this post was submitted on 14 Nov 2023
43 points (93.9% liked)

Python

6230 readers
4 users here now

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

πŸ“… Events

October 2023

November 2023

PastJuly 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
43
Python errors as values (www.inngest.com)
submitted 10 months ago by mac@programming.dev to c/python@programming.dev
18 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] onlinepersona@programming.dev 1 points 10 months ago (2 children)

If only python had a throws keyword like in Java. They got that right at least.

[–] eager_eagle@lemmy.world 3 points 10 months ago* (last edited 10 months ago) (1 children)

raise and raise ... from ?

[–] dozymoe@mastodon.social 3 points 10 months ago (1 children)

I think they meant the registration of what Exceptions a function can possibly throw.

@eager_eagle @onlinepersona

[–] eager_eagle@lemmy.world 1 points 10 months ago

ah yes - that's useful

[–] sugar_in_your_tea@sh.itjust.works 1 points 10 months ago* (last edited 10 months ago)

I disagree, I hate that keyword. Exceptions should be... exceptional, and regular errors should be data. I only want to see exception blocks at top levels for logging and whatnot, everything else should be destructured monads in a match block or similar.

Forgetting a function can throw exceptions is an honest mistake, ignoring errors when you've destructured a return value to get the data is a choice. The former is hard to catch, the latter is plainly obvious in a code review.