Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[DRAFT] [Megathread] Removing the sklearn extensions from the openml-python code base

Abierto
#1,408 12 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Refactorización
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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-python team 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.

Lenguaje dominante
Python
Estrellas
361
Forks
296
Métricas de merge de PR
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openml/openml-python

Todos los issues de openml/openml-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.