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
{{ message }}
Repository navigation
[MNT] Remove __version__.py module and define __version__ in __init__ #1642
Currently, the package defines __version__ inside a __version__.py module and then re-exports it from openml/__init__.py.
This results in two objects named __version__:
the module openml.__version__
the variable __version__ imported from that module
This kind of name masking between a module and a variable is generally discouraged in Python, as it can lead to confusion and unclear import semantics.
This has already been taken. I can see a 2 corresponding 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
Before opening a PR, please leave a quick comment on the issue to indicate you're working on it. That helps avoid duplicated effort and makes it clear who should be credited for the fix.
@Abhishek9639 please read the above comments. this issue already has a PR.
Before opening a PR, please leave a quick comment on the issue to indicate you're working on it. That helps avoid duplicated effort and makes it clear who should be credited for the fix.
Hi! I would like to work on this issue as my first contribution to openml-python.
I plan to remove openml/__version__.py, define __version__ directly in openml/__init__.py, and update any internal imports that depend on the existing module.
I will also run the relevant tests to make sure the package version remains available correctly.
Hi @vasuappu! Thanks for volunteering to work on this issue. Please have a look at the review comment I left on the stale PR (#1653 (review)). It outlines the modern way to store versioning and has references to the relevant PEP/docs. You can set this up as a separate PR (probably better not to continue from #1653).
Activity
amanmurari commentedon Feb 20, 2026
can I work on this Issue
geetu040 commentedon Feb 20, 2026
This has already been taken. I can see a 2 corresponding 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
geetu040 commentedon Mar 5, 2026
There are two PRs open for the same issue:
__version__in__init__.py#1653Before opening a PR, please leave a quick comment on the issue to indicate you're working on it. That helps avoid duplicated effort and makes it clear who should be credited for the fix.
moksha-hub commentedon Mar 5, 2026
@geetu040 Thanks i will drop and close my pr.
Thank you
Abhishek9639 commentedon Mar 6, 2026
@geetu040,
I would love to work on this issue. Could you please assign it to me?
omkar-334 commentedon Mar 6, 2026
@Abhishek9639 please read the above comments. this issue already has a PR.
See this
Abhishek9639 commentedon Mar 6, 2026
Sorry, I didn’t notice that this issue already has a PR. I will look for another issue to work on.
vasuappu commentedon Sep 22, 2026
Hi! I would like to work on this issue as my first contribution to openml-python.
I plan to remove
openml/__version__.py, define__version__directly inopenml/__init__.py, and update any internal imports that depend on the existing module.I will also run the relevant tests to make sure the package version remains available correctly.
Thank you!
PGijsbers commentedon Sep 30, 2026
Hi @vasuappu! Thanks for volunteering to work on this issue. Please have a look at the review comment I left on the stale PR (#1653 (review)). It outlines the modern way to store versioning and has references to the relevant PEP/docs. You can set this up as a separate PR (probably better not to continue from #1653).