Demonstrate Mapping of Python's asyncio to Compute Platform
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python, wasm
- Domain
- backend, developer-experience
Research direction
Start by comparing the Spin SDK's src/spin_sdk/http/poll_loop.py with the async_io definitions in wasm_abi/wit/deps/fastly/compute.wit, then review how componentize-py and Python's asyncio.AbstractEventLoop fit preview2. Done means a defined mapping that lets Python async/await interact with Fastly and third-party code on the supported compute interface.
Written by the indexing model from the issue text.
Description
Many python backend developers may want to use python 3's asyncio in order to interact with fastly and third-party code using async/await. While, at this time, it is unlikely that we'll have significant parallelism outside of what is provided by the platform, this is something that would be a major missing piece as far as developer experience goes.
There's some prior art here for the work required in order to map python's asyncio to something like our WIT async_io definitions by folks at fermyon in the spin sdk (also referenced from compute-sdk-python documentation): https://github.com/spinframework/spin-python-sdk/blob/ffc517a11b2925e9e0338c44d3ce08d75f9fc0a1/src/spin_sdk/http/poll_loop.py
In the case of spin, they are defining an asyncio.AbstractEventLoop subclass. It is likely that with preview3 support this sort of definition may be provided as part of componentize-py; for preview2 compute only supports its bespoke select-ish thing which is what we would have to try to target, but it shouldn't be radically different from wasi:io/poll is my expectation.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fastly/compute-sdk-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fastly/compute-sdk-python#116 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fastly/compute-sdk-python#98 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
fastly/compute-sdk-python#74 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
fastly/compute-sdk-python#61 ·
-
fastly/compute-sdk-python#60 · 1 assignee ·
All issues in fastly/compute-sdk-python
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·