this post was submitted on 12 May 2024
20 points (95.5% liked)

Programmer Humor

32508 readers
636 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] snekmuffin@lemmy.dbzer0.com 2 points 6 months ago (2 children)

Tbf python guidelines encourage it over if/else in cases like this. "Easier to ask for forgiveness than for permission" or something along the lines

[–] lseif@sopuli.xyz 3 points 6 months ago (1 children)
[–] snekmuffin@lemmy.dbzer0.com 1 points 6 months ago

Truers, just mentioning it

[–] bjornsno@lemm.ee 2 points 6 months ago (3 children)

Day 598 of asking for a way to tell which functions throw exceptions in Python so I can know when to wrap in try catch. Seems to me that every other language has this, but when I've asked for at least a linter that can tell me I'm calling a function that throws, the general answer has been "why would you want that?"

How am I supposed to ask for forgiveness if it's impossible to know that I'm doing something risky in the first place?

[–] sqw@lemmy.sdf.org 1 points 6 months ago

cant practically anything throw an exception given the right (sometimes extremely remotely possible) circumstances?

[–] ScreaminOctopus@sh.itjust.works 1 points 6 months ago

Yeah, for this reason I would pretty much never encourage exceptions in Python over some other form of error handling. It's so frustrating when called code throws some random exceptions that are completely undocumented. This is one of the few things Java got (sort of) right

[–] crispy_kilt@feddit.de 0 points 6 months ago (1 children)
[–] bjornsno@lemm.ee 1 points 6 months ago (1 children)

Respectfully, no. Rust is great for some things and Python is great for other things. Switching to rust is not a solution to missing exception linting in another language.

[–] crispy_kilt@feddit.de 1 points 6 months ago

Check it out anyways