Should Docstring contain a 'Raises' statement if the error is handled in the code

Question

Suppose I have a simple function. For example:

def if_a_float(string):
   try:
       float(string)
   except ValueError:
       return False
   else:
       return True

Should I include the Raises: ValueError statement into my docstring or should I avoid it as the error was already handled in the code? Is it done for any error (caught/uncaught)? I do understand that it probably depends on the style, so let's say I am using the Google Docstring style(though I guess it doesn't matter that much)

Answer 1

You should document the exception raised explicitly, as well as those that may be relevant to the interface, as per the Google Style Guidelines (the same document you mention yourself).

This code does not raise an exception explicitly (there is no raise), and you do not need to mention that you are catching one. Actually, this code cannot even accidentally raise one (you are catching the only line that could) and therefore it would be misleading if you were to document that the if_a_float() was raising a ValueError.