Closed ChrisBarker-NOAA closed 1 year ago
when you pip install model-catalogues -- it installs the following via pip:
chardet mbstrdecoder typepy datetimerange
I haven't tried using --no-deps to see if it works, nor figured out how these are being brought in.
--no-deps
They are all available via conda-forge
datetimerange is also listed in pip-requirements.txt
datetimerange
This could be some missing deps in the conda packages, but we should probably jsut add them to the conda_requirements.
Also -- a CI set of tests that use conda would be good -- and it should install model_catalogs with --no-deps.
Collecting mbstrdecoder<2,>=1.0.0 Using cached mbstrdecoder-1.1.1-py3-none-any.whl (7.7 kB) Collecting chardet<6,>=3.0.4 Using cached chardet-5.0.0-py3-none-any.whl (193 kB) ... Installing collected packages: chardet, mbstrdecoder, typepy, datetimerange, model-catalogs Successfully installed chardet-5.0.0 datetimerange-1.2.0 mbstrdecoder-1.1.1 model-catalogs-0.2.1.dev5+ga361203 typepy-1.3.0
oops -- wrong repo -- see:
https://github.com/NOAA-ORR-ERD/model_catalogs/issues/25
when you pip install model-catalogues -- it installs the following via pip:
chardet mbstrdecoder typepy datetimerange
I haven't tried using
--no-deps
to see if it works, nor figured out how these are being brought in.They are all available via conda-forge
datetimerange
is also listed in pip-requirements.txtThis could be some missing deps in the conda packages, but we should probably jsut add them to the conda_requirements.
Also -- a CI set of tests that use conda would be good -- and it should install model_catalogs with --no-deps.
Output from pip