Closed sef43 closed 1 year ago
Due to this
This is actually a conda bug. It should not have been able to install the newer incompatible zipp
. Using mamba locally it will complain as expected:
Looking for: ['zipp=3.16']
conda-forge/osx-arm64 Using cache
conda-forge/noarch Using cache
pkgs/main/noarch No change
pkgs/main/osx-arm64 No change
pkgs/r/osx-arm64 No change
pkgs/r/noarch No change
Pinned packages:
- python 3.7.*
Could not solve for environment specs
Encountered problems while solving:
- package zipp-3.16.0-pyhd8ed1ab_0 requires python >=3.8, but none of the providers can be installed
The environment can't be solved, aborting the operation
Not sure how the CI conda managed to create the failing environment.
Regardless, if we update the minimum python version to 3.8 it should fix this. Python 3.7 is no longer supported https://devguide.python.org/versions/
Dropping 3.7 would be reasonable.
looks to be fixed in the upstream conda package
The CI has started failing for all cases. My guess is this is caused by an update in one of the upstream packages (maybe pytest itself?):