Python

6380 readers

103 users here now

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

📅 Events

Past

November 2023

PyCon Ireland 2023, 11-12th
PyData Tel Aviv 2023 14th

October 2023

PyConES Canarias 2023, 6-8th
DjangoCon US 2023, 16-20th (!django 💬)

July 2023

PyDelhi Meetup, 2nd
PyCon Israel, 4-5th
DFW Pythoneers, 6th
Django Girls Abraka, 6-7th
SciPy 2023 10-16th, Austin
IndyPy, 11th
Leipzig Python User Group, 11th
Austin Python, 12th
EuroPython 2023, 17-23rd
Austin Python: Evening of Coding, 18th
PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th

August 2023

PyLadies Dublin, 15th
EuroSciPy 2023, 14-18th

September 2023

PyData Amsterdam, 14-16th
PyCon UK, 22nd - 25th

🐍 Python project:

💓 Python Community:

#python IRC for general questions
#python-dev IRC for CPython developers
PySlackers Slack channel
Python Discord server
Python Weekly newsletters
Mailing lists
Forum

✨ Python Ecosystem:

🌌 Fediverse

Communities

#python on Mastodon
c/django on programming.dev
c/pythorhead on lemmy.dbzer0.com

Projects

Pythörhead: a Python library for interacting with Lemmy
Plemmy: a Python package for accessing the Lemmy API
pylemmy pylemmy enables simple access to Lemmy's API with Python
mastodon.py, a Python wrapper for the Mastodon API

Feeds

founded 1 year ago

MODERATORS

jnovinger

erlingur

norambna

Python errors as values (www.inngest.com)

submitted 1 year ago by mac to c/python

18 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] onlinepersona 1 points 1 year ago (2 children)

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

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

raise and raise ... from ?

[–] [email protected] 3 points 1 year ago (1 children)

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

@eager_eagle @onlinepersona

[–] [email protected] 1 points 1 year ago

ah yes - that's useful

[–] [email protected] 1 points 1 year ago* (last edited 1 year 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.