Replies: 3 comments 3 replies
-
|
Yes, providing a unified dependency abstraction is indeed the goal. The problem is, I know nothing about Celery. This is something a domain expert will have to at least design. |
Beta Was this translation helpful? Give feedback.
-
|
I took a stab at writing this! I am certainly not an expert with Celery internals, though. https://github.com/atbigelow/svcs/tree/celery-integration How to get proper hooks into Celery for holding I am going to keep working on this to see if this really is the best way to hook in. But do plan on making a PR in the near future. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds great! That's the recommended route, so I'll do that. Maybe a side discussion to have about how best to surface these not-included integrations for visibility and ease of discovery. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be cool to be able to request svcs for the lifetime of a Celery task. The idea of having this was actually what really drove the point home for me as to why svcs is an awesome idea; I have a Flask + Celery codebase and it would be amazing to be able to use utility functions that grab svcs in the correct way for themselves depending on which context they're called in.
Beta Was this translation helpful? Give feedback.
All reactions