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
At GH-874, we discovered that the installation of the wradlib package is performed seperately from the package version pinned in poetry.lock. This is why we we were getting a build error 1, because it installed the most recent wradlib 1.19.0, which apparently has an installation flaw (GH-876).
The issue has been quickly fixed with 2f79c5b now, but the situation should be improved by completely getting rid of the separate pip invocation. I currently can't remember why it is there. It would be better to install wradlib as a regular optional dependency of wetterdienst, right?
Wradlib was previously installed decoupled of wetterdienst because it had gdal in its dependencies, and only after Kai had opted out GDAL from wradlib we were able to install it directly via pip. I had also tried to put it as is in pyproject.toml but the --no-deps option was seemingly not available there.
At GH-874, we discovered that the installation of the
wradlib
package is performed seperately from the package version pinned inpoetry.lock
. This is why we we were getting a build error 1, because it installed the most recent wradlib 1.19.0, which apparently has an installation flaw (GH-876).The issue has been quickly fixed with 2f79c5b now, but the situation should be improved by completely getting rid of the separate
pip
invocation. I currently can't remember why it is there. It would be better to install wradlib as a regular optional dependency of wetterdienst, right?wetterdienst/.github/release/full/Dockerfile
Lines 16 to 17 in 40b5800
wetterdienst/.github/workflows/install.sh
Line 18 in 40b5800
/cc @neumann-nico
Footnotes
https://github.com/earthobservations/wetterdienst/actions/runs/4193227334/jobs/7269833277#step:7:1151 ↩
The text was updated successfully, but these errors were encountered: