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

server: entrypoints `run_*.py` are written as scripts

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

维护者通常 4 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
74/100
Issue 类型
重构
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

Start by reading server/app/services/run_repository.py, run_registry.py, and run_discovery.py to identify the code currently executed at import time. Move each entrypoint's setup into a main() function and only assign application when the script is run directly. Done when importing these modules no longer executes the setup, while direct execution still creates the WSGI application.

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

描述

enhancement server

To create the Python WSGI application, the docker images execute a script from server/app/services (run_repository.py, run_registry.py, run_discovery.py) which sets the global application variable.
These script's code is written directly to the file and is not wrapped inside functions or a if __name__ == "__main__" guard. Therefore this code can only and will always be executed when the script is imported (e.g. import app.services.run_repositroy). This complicates unit testing unnecessary, because it requires re-importing the script over and over again.

We should wrap the code that lives at file level today inside a main() function and only execute it, when the script is run directly. This could look equivalent to this:

def main() -> WSGIApp:
	...
	
if __name__ == "__main__":
	application = main()
主要语言
Python
星标
104
派生
56
平均合并
12 天 13 小时
30 天内合并 PR
5

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

eclipse-basyx/basyx-python-sdk 的其他 Issue

查看 eclipse-basyx/basyx-python-sdk 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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