First up, congrats on your first FLOSS project: a decent one at that! I wish you plenty of users and a contributor or two :) I also like that you are aiming f

First up, congrats on your first FLOSS project: a decent one at that! I wish you plenty of users and a contributor or two :) I also like that you are aiming for functional API: as you note yourself, that makes it easier to test and understand the code. The problem I have with the approach is that, instead of reducing, you are actually increasing the amount of magic in DRF. The direction I'd like to see Python projects go is more towards less magic (decorators are almost always side-effect heavy, modifying and augmenting in-place things they decorate, and those parts are rarely, if ever, tested). Basically, if DRF was done in a simpler way, there would be no need for your project since it would be obvious how to achieve the same (simpler!) thing with DRF directly. Again, this is coming from a Python veteran of 20 years who has seen Python's adaptability and dynamism take projects in all sorts of ingenious directions. But none of them has led to readable and maintainable code. Another thing that's a problem with magic is that seemingly simple functional test that should take all of 0.5ms to run is going through a bunch of code paths: this approach leads to those 2h test suites on larger projects.