thanks for addressing the issue. imo however, we need a generalized approach (alike dependency_injection), that could then be re-used in several parts of the library's code and extensions.

if it's agreed to include such funtionality, it should be merged after a 1.2 release. it adds complexity, opens new opportunies and should thus be tested broadly by the community.

Yes, I'm going to release 1.2, then you guys can start working on this. Thanks @harvimt for starting work on the feature.

btw, i recently made use of such mechanics in inxs. it actually is pretty straight-forward and fun to use. however we must be aware that it adds some overhead. also, would we implement our own inspection or use the package mentioned above? i tend to the first option.

yes, inspect is a stdlib module. but comfortable signature inspection has been added with Python 3.3. as Python 2 is still supported by cerberus, we'd have to implement that part too.

meh, forget it, getfullargspec should be sufficient as type annotations are not relevant for this use-case.

why would you "write your own inspection"?

i actually meant 'injection'! :-/

this could be an opportunity to start a discussion and layout a maintenance plan of future versions with regard to Python 2. in a seperate issue, @nicolaiarocci what do you think, shall i draft a rough sketch to start this?

this could be an opportunity to start a discussion and layout a maintenance plan of future versions with regard to Python 2. in a seperate issue, @nicolaiarocci what do you think, shall I draft a rough sketch to start this?

Yes.