FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
| from celery import Task | |
| from celery.task import task | |
| from my_app.models import FailedTask | |
| from django.db import models | |
| @task(base=LogErrorsTask) | |
| def some task(): | |
| return result | |
| class LogErrorsTask(Task): |
| # This is a very crud example of using the Repository Pattern with SQLAlchemy. It allows me to completely ignore interactions with | |
| # the database. This is only pulled in whenever I require to persist or retrieve an object from the database. The domain/business | |
| # logic is entirely separated from persistence and I can have true unit tests for those. | |
| # The tests for persistence are then limited to very specific cases of persistence and retrieving instances, and I can do those | |
| # independent of the business logic. They also tend to be less tests since I only need to test them once. | |