That's a pretty strong opinion. You do understand the ease of use issues, right? I'm not sure this case is against best practices because what we really have here is ElasticUtils the framework agnostic library and the Django layer on top of it, but we package both in the same repository. If I had more time to spend, I'd split them into two separate libraries. But that's a pain in the ass maintenance-wise. Regardless, that's how I'm treating them.