My Python libraries often tend to be structured like this:
One package called like the_task_specific_tools. This package contains a collection of functions doing the actual work. The functions might be complicated, but there's just a minimum of "architecture", normally they are just plain functions. That allows me to combine those valuable functions in whatever architecture/facade suitable for further use, or to use them directly.
A second package (or more of them) is called like facade_for_that_task. This package will build an architecture/facade/API around the basic functions, normally suitable for a somewhat specific use case.
I think in classical design pattern theory, one would call the first package something like an "implementation" and the second one a "facade".
But does this architecture pattern have a specific name/naming convention in Python? I'm also open for some good names for the two packages, even if not very official.
Aucun commentaire:
Enregistrer un commentaire