I can confirm the behavior described at the question post. I think that the only way to notice the developer that the static abstract method should be implemented in a subclass is to raise the NotImplementedError in the declared method in the ABC. Unfortunately, the error happens only at runtime.