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

Python client in VISOR

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

The issue identifies the VISOR Python client and PIM's existing CLI calls, but names no files or tests. Start by locating the CLI entry points and the PIM call sites, then trace how VISOR is invoked today. Done means VISOR has a Python client and all PIM calls use it instead of the CLI; check the compatibility requirement between new PIM versions and the latest VISOR release.

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

描述

technical
📝 Description of the feature

Currently, the PIM implementation calls the cli tool.
The cli tool was never meant to be used that way - it was more of an internal dev tool. In order to have a more stable implementation, we should add a python client on VISOR, so that PIM can call directly this client and not the cli tool.

The work is broken into 2 steps:

  1. in VISOR, create this python client
  2. re-implement PIM to use the new client instead of cli

Note that this will break backward compatibility on the PIM side: new PIM versions will have to use the latest VISOR release with the new python client.

Acceptance Criteria

A python client exists in VISOR. All the PIM calls have been reimplemented to use this python client instead of the cli.

💵 Business Value

No response

🔗 Useful links and references

No response

主要语言
Python
星标
2
派生
1
平均合并
3 天 6 小时
30 天内合并 PR
29

环境准备

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

从这里开始

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

ansys/Visual-Interactive-Simulation-Object-Renderer 的其他 Issue

查看 ansys/Visual-Interactive-Simulation-Object-Renderer 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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