Open dylanmcreynolds opened 1 week ago
Did it happen when installing into an existing environment with some conflicting packages?
The latest version of https://anaconda.org/conda-forge/tiled-base/files (v0.1.0b8) has the following dependencies:
appdirs, awkward, click !=8.1.0, dask, httpx >=0.20.0, json-merge-patch, jsonpatch, jsonschema, lz4, msgpack-python >=1.0.0, ndindex, numpy, orjson, pandas, pyarrow, python >=3.8, python-blosc2, pyyaml, sparse >=0.13.0, typer, xarray, standard
Confirming that I get the same result from a fresh conda environment. I can work around it by specifying a minimum version, but I'm not sure why conda is prioritizing alpha over beta.
Conda can see all of the available versions, including beta versions.
Can limit to just the beta versions.
% conda search -c conda-forge 'tiled>=0.1.0b'
Loading channels: done
# Name Version Build Channel
tiled 0.1.0b1 hd8ed1ab_0 conda-forge
tiled 0.1.0b2 hd8ed1ab_0 conda-forge
tiled 0.1.0b4 hd8ed1ab_0 conda-forge
tiled 0.1.0b5 hd8ed1ab_0 conda-forge
tiled 0.1.0b6 hd8ed1ab_0 conda-forge
tiled 0.1.0b7 hd8ed1ab_0 conda-forge
tiled 0.1.0b8 hd8ed1ab_0 conda-forge
The Tiled README has instructions for installing tiled from conda-forge. Someone here tried that today, and got tiled
0.1.0a117
. The current release isv0.1.0b8
. We noticed this because the old version of tiled has issues withnumpy 2.x
I don't know if the fix is to update the readme and remove the conda-forge instruction or to fix the conda-forge release.