add requeueing in background#12
Conversation
|
Is it WIP? |
mesher-x
changed the title
mesher-x
changed the title
|
Also please update a README file. Ideally show some usage example there. |
| be renamed into `put_nowait`. | ||
| - `get_multi` and `put_multi` methods, allowing getting and putting multiple | ||
| items from queue with one call | ||
| - method for periodical requeueing of not acknowledged tasks |
There was a problem hiding this comment.
Please add at least minimal usage example
|
|
||
|
|
||
| class Stopped(Exception): | ||
| pass No newline at end of file |
|
|
||
| def put(self, task, method='lua'): | ||
| if self._is_stopped: | ||
| raise exceptions.Stopped |
There was a problem hiding this comment.
This is an error: you are rising an instance of type type. (Pylint should be able to find this)
| ) | ||
|
|
||
| def _ack(self, task_id, method='multi'): | ||
| if self._is_stopped: |
| ) | ||
|
|
||
| def stop(self): | ||
| if self._is_stopped: |
There was a problem hiding this comment.
that one too (it is OK to call .stop() multiple times)
|
|
||
| if self._requeue_interval != 0: | ||
| self._regular_requeue_task = \ | ||
| self._loop.create_task(self._requeue_regularly()) |
There was a problem hiding this comment.
Hmm.
Creating a task in constructor doesn't feel right. Especially if we have to call .stop() afterwords (we did't .start() or .run() anything, right?).
There was a problem hiding this comment.
When we call __init__ it is not guaranteed that loop is activated and redis has connection (although it wouldn't be a very popular use case).
So we have three options:
- start periodic task only when some other method called,
requeue_interval != 0and correspondingfutureisNone(not really a great idea but will kind of work) - Wrap everything into
__aenter__and__aexit__so to use an instance one will have to call create it withasync with. It is unclear whether we should or should not support calls outsideasync withblock. - Provide
__aenter__and__aexit__only for periodic task. This is a little bit more flexible option for user as periodic task can be stopped and started multiple times. But it is kind of harder to implement: We need to provide separate class (asynchronous context manager which would implement those magic methods) for this particular case.
There was a problem hiding this comment.
Probably the easiest way for now is to provide run_periodic() method that will have requeue_interval argument. Corresponding stop_periodic() will have obvious semantics. Your more general .stop() method will have to go to a different pull request (or to /dev/null)
2 participants
No description provided.