How to use generated exceptions

So I’m trying to use SSM and catch scenario where value doesn’t exist. The call generates botocore.errorfactory.ParameterNotFound: An error occurred (ParameterNotFound) when calling the GetParameter operation

The thing is that ParameterNotFound does not exist the class with the error is dynamically generated and I can’t reference it in the code (or at least not from botocore.errorfactory.ParameterNotFound). What’s the point of having exceptions like this when they can’t be caught? Why bothering with dynamically generated class, when you could just have a generic error and inside of its properties I could extract the actual cause. Or is there a way to use it that I’m not aware of?

[takeda]

Yes, this is what I ended up doing, my point is that those dynamically generated classes for exceptions are pointless. You don’t have a static class that you can use to catch them, thankfully they all inherit from ClientError so one can catch them the way you showed the problem is that when you see botocore.errorfactory.ParameterNotFound it’s not obvious how to handle it. You don’t know that it inherits from ClientError and you don’t know that exception name could be the error code. I would like to propose abolish the dynamic classes and simply raise ClientError so it shows ClientError('ParameterNotFound', ...) or similar that makes it clear what exception happened and how to catch it.

[swetashre]

@takeda - Modeled exceptions can be accessed through the client. Instead of botocore.errorfactory.ParameterNotFound you can do client.exceptions.ParameterNotFound.

client = boto3.client('ssm')

try:
   response = client.get_parameter(Name='sweta')
except client.exceptions.ParameterNotFound as e:
    print(e)

I agree that this is confusing and the current documentation is insufficient. More information on this can be found at this pr: boto/botocore#1113 .