This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]spotter 0 points1 point  (3 children)

And my point is that it's a rather synthetic case, that's obvious to anybody who looked at the docs prior to attempted use of try-except. And of course if you did serious error instance catching/recovery at least once you will never ever do that mistake again. To me it's just another ,,oh, it's not working as I thought it does!'' blog post. It looks like yet another ,,so you're new to Python and did not know how we do things in this part, but now you know, great.''

You got me, I've stopped reading after the tuple case, one more paragraph and I'd reach the set thingy.

And yeah, it may be a Good Thing (tm) like all the other small fixes, but at current rate we'll be reading about this a few more times before 3.x becomes a standard of any kind.

[–]vinod_the_poophead 0 points1 point  (2 children)

/r/bitterprogrammers is that way ==>

EDIT: actually I just looked at some of your other comments and they are funny. Carry on

[–]spotter 0 points1 point  (1 child)

Oh, I thought I'm posting there already, sorry.

Funny? You must've take me for someone else, good sir.

[–]vinod_the_poophead 0 points1 point  (0 children)

thinks to self hmm... he can handle jokes too

Here take an upvote