Python Client ETA?


#1

There are mentioned of Python Client in the pipeline:


“I’m working on a Python client with one of my colleagues but haven’t put it out there yet”

Blog on Python Client stub: it’s more than enough to get going.

What would be a good way for Python worker to be notify of job instead of polling?


#2

Hi @snowman, unfortunately, we haven’t had much time to work on the Python client in the past few months and still haven’t put anything out there (it’s still merely a side project / would be a community contribution for https://awesome.zeebe.io).

Regarding polling and clients in general: we’ve heard feedback that users would prefer a different approach than what Zeebe does currently for a number of (perfectly valid) reasons, and as a first step, we’re looking into a long polling feature. We wouldn’t start on this until at least Q3, but it is definitely on our radar.

Curious to know, are you running into issues with latency and/or resource utilization due to the current polling approach?

Regards,
Mike


#3

Thank you @wints !
Focus on core functionality make perfect sense to me.
Since Zeebe are in developer preview stage; releasing a “unfinished” client might not be a bad idea to draw participation from wider community.

Not running into any issue right now for exploratory use cases.
There is always an element of premature optimizations on my part.

On the other hand; reduce stack complexity is always good IMHO:
There are mention of Python Celery in one of the thread. If I can replace [Celery/RQ/Async Worker] with Zeebe while adding functionality is very attractive. It goes well with the the “battery included” approached.

Best,
David


#4

Is this what you are looking for?


#5

thank you @jwulf
I was able to follow along the blog/tutorial and get a simple python worker going.
Maybe I am becoming more paranoid in my old age as the whole endeavor was “too easy” :thinking:

“I don’t know what I don’t know” about what might be missing from a “full feature” client is the reason why I was looking for an official client.

So far so good and no problem to report.


#6

I used that tutorial to write the TypeScript client. It is pretty straight-forward. Zeebe is made up of a handful of simple primitives.