You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenMLSetup should inherit and use methods from OpenMLBase, like every other resource, since it's an independent resource with dedicated schema in backend. Also this will enable tagging which is currently not supported.
Steps:
Inherit OpenMLBase in OpenMLSetup
implement the abstract methods like id, _get_repr_body_fields, ...
OpenMLSetup doesn't support publish, so handle that method accordingly
Add a test file tests/test_setups/test_setup.py and write unitests for OpenMLSetup there
This has already been taken. I can see a PR (actually 2 PRs).
You can may be take a look at other issues, or review these PRs with your suggestions.
In-case you are looking for good-first-issues, you can look find them here: Good First Issues
Here are some more umbrella issues: #1649, #1633
Thanks for taking the time to create the issue, due to being flooded with notifications at the time I unfortunately missed the ping.
I do not think that a setup should be treated the same as the other "main" objects. As I wrote in #1648 we are likely doing away with this concept (at least as far as the clients are concerned). Moreover, even in the current state they have some differences that would make it inappropriate to inherit from the base class: they cannot be published directly and they do not have their own dedicated webpage (openml_url).
Activity
Premkumar-2004 commentedon Feb 19, 2026
hey can i work on this issue ?
geetu040 commentedon Feb 19, 2026
This has already been taken. I can see a PR (actually 2 PRs).
You can may be take a look at other issues, or review these PRs with your suggestions.
In-case you are looking for good-first-issues, you can look find them here: Good First Issues
Here are some more umbrella issues: #1649, #1633
feat: implement tagging for setups (openml#1648, openml#1647)
PGijsbers commentedon Oct 15, 2026
Thanks for taking the time to create the issue, due to being flooded with notifications at the time I unfortunately missed the ping.
I do not think that a setup should be treated the same as the other "main" objects. As I wrote in #1648 we are likely doing away with this concept (at least as far as the clients are concerned). Moreover, even in the current state they have some differences that would make it inappropriate to inherit from the base class: they cannot be published directly and they do not have their own dedicated webpage (openml_url).