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

Discussion: blueapi plan renaming

未关闭
  • 哪里不对？
#1,701 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 7 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

The issue is a design discussion, not a settled change. Start with the plan-registration code in blueapi that reads the __name__ of an imported plan, and with the __init__.py re-export pattern shown in the issue. Done would mean a maintainer-agreed approach, such as an explicit registration name or a wrapper, before any implementation begins.

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

描述

On i15-1, we've tried to do

from .data_collection import (
    data_collection as single_temperature_collection,
)

__all__ = ["single_temperature_collection"]

in the hope that we could rename our plan as seen inside blueapi. However, the registered plan name is still data_collection inside blueapi, I'm guessing because blueapi uses the __name__ attribute of the imported object to decide this.

There are use cases when you may want to register a plan under a different name inside blueapi, for example if you want the plan called one thing for internal use as a subplan, but something else when exposed to users.

Having said this, maybe the simplest solution is just to wrap plans when we want to do this. Interested on other people's thoughts

主要语言
Python
星标
13
派生
14
平均合并
8 天 7 小时
30 天内合并 PR
5

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

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

DiamondLightSource/blueapi 的其他 Issue

查看 DiamondLightSource/blueapi 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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