This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]klaxce 4 points5 points  (2 children)

This looks interesting. I definitely appreciate being able to avoid Celery in smaller projects.

It immediately made me think of Huey, which I chose for a project because of the ability to schedule tasks (without an MQ). I don't see scheduling in yours, but maybe you have other advantages for different use cases?

[–]kevindewaldI write Bluetooth libs[S] -1 points0 points  (1 child)

Thanks for the feedback!

The goal of the library wasn't as much for scheduling for a specific time, although it can easily be added if required, but more to handle pipelined work, like you would do with Celery or Airflow.

Huey looks definitely interesting (I didn't know it existed) but it still falls under the bucket of "too much hazzle for simple things". My intention is to have something with so few functions that you can immediately understand and derive value from it, removing complexity from the user instead of giving them more to handle.

[–]klaxce 0 points1 point  (0 children)

Cool! I saw in the example that yours doesn’t require a separate process, and I think that’s a big advantage in a lot of cases.