pre_process and process methods optional implementation should be handled

[Colin-b]

As they are dynamically retrieved via getattr, the fact that they are not implemented should be properly handled instead of raising the default exception from getattr.

We should also consider defaulting to a rejection pre-processing in case there is no processing implementation ?

[stan-janssen]

What issue are you running into specifically? The Exception is thrown at load time, if you attempt to create a subclass of the abstract base class. I want to enforce that people at least think about implementing all possible messages for a role, which is why I am enforcing the developer to implement all the process_ methods.

Or maybe I'm misunderstanding what you're asking?

[Colin-b]

The wording of the request is quite poor indeed. Let me rephrase it:

If I only expect a subset of messages as a dedicated role, I would like to only need to implement handling of those messages. While keeping the ability to override the default behavior (and default would be whatever you feel like, from raising an exception to logging an error).