Closed mrocklin closed 3 years ago
Hrm, I'm not able to reproduce solving for Windows locally:
In [6]: env
Out[6]:
{'name': 'notebook',
'channels': ['conda-forge', 'defaults'],
'dependencies': ['python=3.8',
'pip',
'python-blosc',
'cytoolz',
'dask=2.23.0',
'lz4',
'numpy>=1.19.0',
'pandas>=1.1.0',
'bokeh>=2.1.1',
'dask-image>=0.3.0',
'dask-ml>=1.5.0',
's3fs',
'numba',
'pyarrow>=0.15.1',
'scikit-learn>=0.23.1',
'h5py',
'xarray',
'bottleneck',
'requests',
'nodejs',
'jupyterlab',
'nb_conda_kernels',
'dask-labextension']}
In [7]: solve = conda.api.Solver(prefix="-not-an-environment-", subdirs=["win-64", "noarch"], channels=env["channels"], specs_to_add=env["depen
...: dencies"]).solve_final_state()
Collecting package metadata (repodata.json): done
Solving environment: -
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
Examining numba: 92%|█████████████████████████████████████████████████████████████████████████████████▌ | 22/24 [00:57<00:05, 2.56s// ]
I get the same result with conda 4.8.3 and 4.8.4 (latest release on conda-forge). What channel was conda
installed from? defaults or conda-forge?
Just checking in here. @mrocklin is this still an issue for you? I tried again and am still not able to reproduce a successful solve with conda.api.Solver
Hello, I'm thinking that perhaps the issue you were facing Matt was that the conflicts were being thrown when we used the conda base environment - similar to where we couldn't install s3fs
. Since we are now creating a coiled
environment, this issue should be fixed 🤔
I'm also guessing that this is the case since there were no more updates on the issue 😄
So I have this environment locally
It solves on Windows without a problem
But if I try to solve that same environment with Coiled, it fails to solve on windows
I'm running conda 4.8.3 locally
cc @jrbourbeau