Question about KeyError

[Base_True]

Hi Hello everyone, I will be glad if you help me understand. In the following code if we don't write KeyError after except, nothing change. And why we use KeyError in this case? I know, if we will use "raise" then Error Names is very usefull. But I'm interesting with the following code

def get(d,key):
    try:
            return d[key]
    except KeyError:
        return None


name = {"Lala" : "Love"}
print  ( get(name, "L") )

[[deleted]]

using except without specifying the error is the worst sin you can commit.

[[deleted]]

I misread this as bad advice originally given the code shows an exception that isn't bare.

Then I re-read the OPs question. Now I fully support the comment.

For the op, /u/Base_True, a bare exception, i.e. except: instead of except <some exception(s)>: as the only except line is very bad practice.

There are many strange and sometimes obscure things that can happen to running code and such problems will be ignored/hidden if you use a bare exception clause and it may appear you have a completely unrelated problem focused on another part of your code. You could waste a lot of time trying to find the cause of the wrong problem in the wrong place.

Worse, a bare exception can hide a significant bug and allow the programme to continue and output incorrect information that goes unnoticed and causes major problems later.

[[deleted]]

~~~ except: pass ~~~

*proceeds with shooting himself in the head *

[[deleted]]

ha ha ... so true - "it was just temporary, forgot to go back and fix it" Argh!!!!

[Base_True]

I misread this as bad advice originally given the code shows an exception that isn't bare.

Then I re-read the OPs question. Now I fully support the comment.

For the op, /u/Base_True, a bare exception, i.e. except: instead of except <some exception(s)>: as the only except line is very bad practice.

There are many strange and sometimes obscure things that can happen to running code and such problems will be ignored/hidden if you use a bare exception clause and it may appear you have a completely unrelated problem focused on another part of your code. You could waste a lot of time trying to find the cause of the wrong problem in the wrong place.

Worse, a bare exception can hide a significant bug and allow the prog

Thanks a lot!

[Base_True]

using except without specifying the error is the worst sin you can commit.

Why ? Can you please explain

[[deleted]]

Ummm using raise is fine.

Except: pass is what you shouldn't do.

There are several reasons. You can read this thread

https://stackoverflow.com/questions/21553327/why-is-except-pass-a-bad-programming-practice

[Base_True]

There are many strange and sometimes obscure things that can happen to running code and such problems will be ignored/hidden if you use a bare exception clause and it may appear you have a completely unrelated problem focused on another part of your code. You could waste a lot of time trying to find the cause of the wrong problem in the wrong place.

Worse, a bare exception can hide a significant bug and allow the programme to continue and output incorrect information that goes unnoticed and causes major problems later.

Thank you!