You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
automatminer causes needless recurring warnings when updating packages it depends on:
pip install crystal-toolkit
[...]
automatminer 1.0.3.20200727 requires matminer==0.6.2, but you'll have matminer 0.6.5 which is incompatible.
automatminer 1.0.3.20200727 requires pymatgen==2020.01.28, but you'll have pymatgen 2022.0.5 which is incompatible.
automatminer 1.0.3.20200727 requires scikit-learn==0.22.2, but you'll have scikit-learn 0.24.1 which is incompatible.
I believe the way to fix this is to simply specify dependencies with >= rather than == in requirements.txt. Will submit PR.
The text was updated successfully, but these errors were encountered:
I will update the dependencies soon (hopefully resolving some of the incompatibilities) but I am a big weary about changing everything to >=. I have not tested it yet but I suspect that will break some things. Considering the large number of things automatminer does in a pipeline (many of which rely on a lot of different libraries) it seems like this could cause some instability. But if you have a PR with the updated requirements that passes CI and is relatively stable, I'm all ears!!
You should test against pinned versions in requirements.txt, but have compatible version ranges in setup.py where you can use both >= and < to ensure you have compatible versions ranges. This is causing problems in the MP Workshop repo for auto-updates for instance.
automatminer
causes needless recurring warnings when updating packages it depends on:I believe the way to fix this is to simply specify dependencies with
>=
rather than==
inrequirements.txt
. Will submit PR.The text was updated successfully, but these errors were encountered: