Manuel Astudillo

@vraj-fyno not sure what I should look for about this issue. Why don't you use the example code from the documentation instead of writing your own that does not work?

You say that this code is not working: https://docs.bullmq.io/python/introduction Then you paste some random code that is not working. 🤔

The Python version is still under heavy development, so most users using it right now are NodeJS users that need interoperability with Python. We will improve the documentation as the...

If you take code from the tests it is not going to work as those tests are written to test some specific edge cases, so you would not write code...

Thanks, I improved the documentation a bit based on your feedback. However a couple of things: - token is still omitted as it is only needed when processing jobs manually,...

If you remove the loop then you must also add logic to close the worker when necessary, as the code in the example will just continue with ```worker.close()``` and then...

@cagejsn thanks!

I am closing this as the examples should be correct now, if something is wrong please open a new issue.

Not sure what is the difference, but we have a test that precisely test the scenario you are presenting in your issue: https://github.com/taskforcesh/bullmq/blob/master/tests/test_worker.ts#L467

@SamBallantyne you need to return a future I think, so just printing to the console may not be correct.