This is... OK. Ideally, you would have separate exceptions for each reasonably distinct situation (e.g. one exception for all "the config file is malformed" errors, reuse FileNotFoundError in 3.x for "the config file doesn't exist", etc.). But this is one of the more innocuous forms of technical debt.
The downside is that if you ever do introduce those separate exceptions, they may need to subclass from RuntimeError for reasons of backwards compatibility. That's kind of ugly, but mostly harmless.
exception - Python: is RuntimeError acceptable for general use? - Stack Overflow
Meaning of RuntimeError
What is runtime error and how to solve it?
Runtime warnings in Python
I am a noob and just started solving leetcode. But today I solved 2 medium difficulty questions which were running fine but when I submitted them it was showing runtime error (both were showing different runtime errors) . The solution was also very similar to mine but couldn't do it because of runtime error. Please help