Open tm-slavik57 opened 5 months ago
Seems like it's a bug with the sktime
conda package recipe, it uploaded the dependencies for windows with an extra comma ,
for the pycatch22
library.
('pykalman >=0.9.5', 'pmdarima >=1.8.0,!=1.8.1,<3.0.0', 'stumpy >=1.5.1', 'pycatch22 >=0.4,<0.4.4,', 'prophet >=1.1', 'scikit-posthocs >=0.6.5', 'filterpy >=1.4.5', 'pystan ==2.19.1.1', 'pyod >=0.8.0', 'statsmodels >=0.12.1', 'tbats >=1.1.0', 'hmmlearn >=0.2.7', 'numba >=0.53', 'tslearn >=0.5.2,<0.7.0', 'seaborn >=0.11.0', 'kotsu >=0.3.1', 'tsfresh >=0.17.0', 'gluonts >=0.9.0', 'esig ==0.9.7', 'statsforecast >=0.5.2,<1.8.0', 'matplotlib-base >=3.3.2')
It would be great to add a protection against such cases.
If there is an issue with the dependencies of a package then I would print a log about the library name and the issue with the dependency. But, if the specific package version is not required then I wouldn't fail the entire resolution, I would skip the problematic version
To add a few things here:
conda-forge
, so it may have to do with conda-forge
rather than with conda
. I am not an expert on either, just wanted to raise this.conda-forge
recipe is in this PR: https://github.com/conda-forge/sktime-feedstock/pull/117@tm-slavik57,
Just curious, is this issue happening with the libmamba
solver, the classic
solver or both?
To test, you could run the install commands with either --solver=libmamba
or --solver=classic
to see which one is affected.
@tm-slavik57,
Just curious, is this issue happening with the
libmamba
solver, theclassic
solver or both?To test, you could run the install commands with either
--solver=libmamba
or--solver=classic
to see which one is affected.
@travishathaway
Running with libmamba
solver worked, running with the classic
solver failed as described above
I see!
So: 1. it is a conda
issue after all, and 2. this explains it why, at 50-100.000 conda downloads a month, no one has complained earlier...
@tm-slavik57,
Thanks for reporting back. Currently, the preferred work around for this issue will be to upgrade to the libmamba
solver. I bring this issue up with the other maintainers to see if this is something we want to consider working on.
@travishathaway For now I patched the package on conda-forge: https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/706 So for now there is no issue to work around, but I think it is still worth solving
Moved to conda-build so we can look into adding MatchSpec
linters to check for bad specs when building packages.
Checklist
What happened?
When creating an environment it fails with:
The minimal environment file to reproduce:
I ran the command:
Conda Info
Conda Config
Conda list
Additional Context
The only thing I found in the sktime repo related to the error is this line which seems legit:
https://github.com/sktime/sktime/blob/31dd08f10a942f9034a71c0bcf3bffc4e158cb57/pyproject.toml#L213C3-L213C27
Perhaps the
22
in thepycatch22
package name messes things up 🤷Edit It happens only on windows, on linux it works fine