Skip to content

module_available gives inaccurate version info #10335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
d-v-b opened this issue May 19, 2025 · 2 comments
Closed

module_available gives inaccurate version info #10335

d-v-b opened this issue May 19, 2025 · 2 comments
Labels
plan to close May be closeable, needs more eyeballs

Comments

@d-v-b
Copy link
Contributor

d-v-b commented May 19, 2025

What is your issue?

importlib.metadata.version is not always right:

>>> from importlib.metadata import version
>>> version('zarr')
'2.16.2.dev35+dirty'
>>> import zarr
>>> zarr.__version__
'3.0.5.dev88+g8af0ce42'

see an older discussion of this behavior here

I don't know if there's a fix besides try... except around an import statement? But this issue prevents xarray from seeing my local zarr v3 install, which prevents me from debugging zarr v3 issues.

@d-v-b d-v-b added the needs triage Issue that has not been reviewed by xarray team member label May 19, 2025
@dcherian
Copy link
Contributor

This is almost certainly due to missing tags.

@dcherian dcherian added plan to close May be closeable, needs more eyeballs and removed needs triage Issue that has not been reviewed by xarray team member labels May 27, 2025
@d-v-b
Copy link
Contributor Author

d-v-b commented May 27, 2025

test.py3.11-1.25-minimal➜  zarr-python git:(main) ✗ git push origin main --tags
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/d-v-b/zarr-python.git
 * [new tag]           v2.18.4 -> v2.18.4
 * [new tag]           v2.18.5 -> v2.18.5
 * [new tag]           v2.18.6 -> v2.18.6
 * [new tag]           v2.18.7 -> v2.18.7
 * [new tag]           v3.0.0 -> v3.0.0
 * [new tag]           v3.0.0-beta.2 -> v3.0.0-beta.2
 * [new tag]           v3.0.0-rc.1 -> v3.0.0-rc.1
 * [new tag]           v3.0.0-rc.2 -> v3.0.0-rc.2
 * [new tag]           v3.0.1 -> v3.0.1
 * [new tag]           v3.0.2 -> v3.0.2
 * [new tag]           v3.0.3 -> v3.0.3
 * [new tag]           v3.0.4 -> v3.0.4
 * [new tag]           v3.0.5 -> v3.0.5
 * [new tag]           v3.0.6 -> v3.0.6
 * [new tag]           v3.0.7 -> v3.0.7
 * [new tag]           v3.0.8 -> v3.0.8

good evidence for the "missing tags" theory! Closing, thanks @dcherian

@d-v-b d-v-b closed this as completed May 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plan to close May be closeable, needs more eyeballs
Projects
None yet
Development

No branches or pull requests

2 participants