Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
#1,408 12 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Refactorisation
Clarté
À clarifier
Activité
À l'abandon
Stack technique
python

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
361
Forks
296
Métriques de merge des PR
Aucune PR mergée en 30 j

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de openml/openml-python

Toutes les issues de openml/openml-python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.