pytest-dev / pytest-dev/execnet
dropping the execmodel concept again
未关闭
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 102
- 派生
- 47
- PR 合并指标
- 30 天内没有已合并 PR
描述
CC @ctheune @nicoddemus
the execmodel concept that @hpk42 introduced back in 2013 has multiple drawbacks
- it breaks execnet for testing qt, as the main thread is no longer under safe control
- it is completely incompatible with the async primitives that are starting to win (asyncio/trio/curio, async/await)
its not quite clear to me for what detailed use-case it was introduced, but as it is right now its a major show-stopper for me to introduce any support for modern async primitives
its the biggest reason why i dropped execnet maintenances, the second biggest reason being that there seemingly where possible placements (unfortunately the replacements turned out not to work out)
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
调研方向
该 issue 没有指出 execmodel 概念对应的文件、测试或入口点。首先定位 execmodel 的实现并查看尚未解决的讨论，然后在尝试进行更改之前，定义受影响的 execnet 行为和兼容性要求。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- distributed-systems
- Issue 类型
- 重构
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100