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
xee is a dependency of geetools. I recently started to pin its version to a lower bound to provide full access to some new features.
Everything works fine in the pip release but I cannot manage to make the conda release to work.
If you look at this build (conda-forge/geetools-feedstock#6) it fails because the installed package METDATA are pointing to version 0.0.0 even though it's the 0.0.14 that get installed.
The conda teams (pinged in the linked PR) told me the recipe is correctly set up and the problem is coming from the xee conda release itself. Can you have a look and maybe make a patch release with the correct metadata ?
The text was updated successfully, but these errors were encountered:
Fixgoogle#161
My understanding of the problem is that the version number is not set anywhere.
pyproject.toml uses a dynamic version number but the dynamic estination is not set, xee package has no __version__ variable. the one in `ext` is using the one from metadata which relies on the pyproject file.
I decided to start this PR by setting where the dynamic version number should come from. Now I need your review to know where the hard coded version number should be set.
xee is a dependency of geetools. I recently started to pin its version to a lower bound to provide full access to some new features.
Everything works fine in the pip release but I cannot manage to make the conda release to work.
If you look at this build (conda-forge/geetools-feedstock#6) it fails because the installed package METDATA are pointing to version 0.0.0 even though it's the 0.0.14 that get installed.
The conda teams (pinged in the linked PR) told me the recipe is correctly set up and the problem is coming from the xee conda release itself. Can you have a look and maybe make a patch release with the correct metadata ?
The text was updated successfully, but these errors were encountered: