[DRAFT] [Megathread] Removing the sklearn extensions from the openml-python code base
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 重构
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- python
调研方向
This is a megathread proposing broad removal of the sklearn extensions, but it names no files, tests, or entry points. Start by identifying all sklearn-extension code and its tests, then map the removal scope and compatibility considerations. Done means the extension code and related content are removed consistently without breaking the remaining openml-python functionality.
由索引模型根据 Issue 内容生成。
描述
We are not planning to support the sklearn extensions in the future.
Currently, the code related to the sklearn extensions within openml-python provides a straightforward way to upload models and results from running sklearn models on OpenML.
Note:
- Even without these extensions, users cannot upload such data to OpenML.
- The sklearn extensions are in the code base of
openml-python, unlike the code for other extensions.
Justification for Removing the Extensions from openml-python
As a result of a recent survey by us (to be published) and our interactions with OpenML and its users, we have obtained a strong signal that this feature is not widely used, if at all, by the broader community. Yet, at the same time, it takes up an enormous amount of overhead during maintenance of OpenML with many lines of code, many tests, and multiple reasons for not being able to upgrade dependencies stemming only from the sklearn extension. Moreover, the sklearn extension has not been maintained or upgraded for a long time.
Previously, a part of the mission statement of OpenML was to enable the reproduction of, for example, old runs via this extension. We do not believe this to be an essential mission statement of the openml-python code. More importantly, the extensions are holding us back and are requiring too many of our already limited resources.
The Way Forward
openml-python will remove all code related to the sklearn extension in a future version
- One will still be able to reproduce the old runs (to some extent) and use the sklearn extension with an older version of
openml-python - If there are users of the sklearn extension, or we see renewed need for this extension, a new project can be created -- similar to the other extensions. However, the current
openml-pythonteam does not commit to supporting this extension.
These issues will serve as a megathread to reference all code removed related to the sklearn extension and any other content that may enable future readers to recreate the sklearn extension in a separate repository.
- 主要语言
- Python
- 星标
- 361
- 派生
- 296
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
openml/openml-python 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
openml/openml-python#1750 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
openml/openml-python#1749 ·
-
难度 1/5 1 小时以内 新手友好度 92/100
openml/openml-python#1746 ·
-
Documentation Good First Issue
难度 2/5 1-3 小时 新手友好度 74/100
openml/openml-python#1708 · 7 条评论 ·
-
Good First Issue module:Run testing
难度 2/5 1-3 小时 新手友好度 82/100
openml/openml-python#1646 · 7 条评论 · 2 个 reaction ·
查看 openml/openml-python 的全部 Issue
相似的 Issue
-
area: harness bug status: needs-triage
难度 2/5 1-3 小时 新手友好度 75/100
Human-Agent-Society/reef#625 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 1/5 1 小时以内 新手友好度 80/100
learningequality/kolibri#15351 · 2 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
-
Name consistency 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
eellak/triplestore#65 · 1 条评论 ·