Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Demonstrate Mapping of Python's asyncio to Compute Platform

未关闭
#12 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python, wasm

调研方向

首先比较 Spin SDK 的 src/spin_sdk/http/poll_loop.py 与 wasm_abi/wit/deps/fastly/compute.wit 中的 async_io 定义,然后审查 componentize-py 和 Python 的 asyncio.AbstractEventLoop 如何适配 preview2。完成的标准是定义出一种映射,使 Python async/await 能够在受支持的 compute 接口上与 Fastly 和第三方代码交互。

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
5
派生
1
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fastly/compute-sdk-python 的其他 Issue

查看 fastly/compute-sdk-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。