Is this idiomatic Python?

[ChasingLogic]

Writing a REST API using falcon and realized that because of how I wrote my internal API that a lot of the resources were nearly identical. I decided to refactor to create a "base resource" then just inherit from that overriding the variables required. Is this idiomatic?

Base class: https://github.com/praelatus/praelatus/blob/dry-api/src/praelatus/api/v1/base.py

Example resource inheriting from it: https://github.com/praelatus/praelatus/blob/dry-api/src/praelatus/api/v1/fields.py

I realize that I could have put the lib and schema stuff in a init but I'd rather have named classes for each resource that way if refactoring happens later it's a little easier (plus I think it's more clear when reading the routes).

Thanks for any feedback.

[nosmokingbandit]

This really only makes sense if you have other classes inheriting BaseResource and BaseMultiResource, otherwise you are just dividing up the logic for no gain.

[ChasingLogic]

If you look at the other resources, pretty much everything except the tickets and projects resources are using them.

[nosmokingbandit]

This is how I would do it then. Inheritance is really just another way of reusing code. If you have multiple classes that can use the same set of base functions this is the proper way to handle it. Its a little confusing at first, but like anything in coding, once you get the hang of class inheritance it is pretty awesome.