sdk-python

There just aren't good Python sandboxing approaches. There are subinterpreters but they can slow to start from scratch. There are higher-level sandboxing approaches like microvms, but they have setup overhead and are not easy to use from inside Python. At Temporal, we required a sandbox but didn't have any security requirement, so we wrote it from scratch with eval/exec and a custom importer [0]. It is not a foolproof sandbox, but it does a good job at isolating state, intercepting and preventing illegal calls we don't like, and allowing some imports to "pass through" the outside instead of being reloaded for performance reasons. 0 - https://github.com/temporalio/sdk-python?tab=readme-ov-file#...

It's very similar - I used Temporal at a previous company to run a couple million workflows per month. The gRPC networking with workers is the most similar component, I especially liked that I only had to worry about an http2 connection with mTLS instead of a different broker protocol. Temporal is a powerful system but we were getting to the point where it took a full-time engineer to build an observability layer around Temporal. Integrating workflows in an intuitive way with OpenTelemetry and logging was surprisingly non-arbitrary. We wanted to build more of a Vercel-like experience for managing workflows. We have a section on the docs page for durable execution [1], also see the comment on HN [2]. Like I mention in that comment, we still have a long way to go before users can write a full workflow in code in the same style as a Temporal

It's probably overkill depending on your use-case, but temporal has a python client: https://github.com/temporalio/sdk-python

> Unless Pydantic is downloading all OS binaries with the package and loading the right one at runtime, this would become a "problem" as well. Nah, it's not that bad. I built a Rust-backed Python library used by many [0], and with setuptools-rust (maturin wasn't flexible enough at the time) and cibuildwheel and GH actions, the wheels are built/shipped with the shared libraries embedded and the end user never has to worry or even be aware of its presence. Pydantic has already been shipping a binary mode with an option for pure Python, so maybe they'll keep the pure Python mode around. 0 - https://github.com/temporalio/sdk-python

It is for this reason in Temporal Python[0], where we wrote a custom durable asyncio event loop, that we maintain strong references to tasks that are created in workflows. This wouldn't be hard for other event loop implementations to do too. 0 - https://github.com/temporalio/sdk-python

We built the logic backing the Temporal Python SDK[0] in Rust and leverage PyO3 (and PyO3 Asyncio). Unfortunately Maturin didn't let us do some of the advanced things we needed to do for wheel creation (at the time, unsure now), so we use setuptools-rust with Poetry. 0 - https://github.com/temporalio/sdk-python

Going to shamelessly plug Temporal’s Python SDK which was designed for asyncio. https://github.com/temporalio/sdk-python Disclaimer: I work for Temporal

hey sorry for taking a while to respond, was busy with personal stuff and hope you see this. 1. yes. its on the order of months. start watching https://github.com/temporalio/sdk-python 2. temporal itself will not produce something like that, because we much rather have a lively community of third party maintainers/startups do that and be their supporters rather than competitors. interested?