Closed unkcpz closed 1 year ago
This is related to the following change:
https://github.com/materialsproject/pymatgen/commit/5b88fc181d8ab97a7d1d3c47692cefdf673888c5
In the latest abipy
version the import has been updated to fix this:
But if your environment still uses an older pymatgen
version due to other package dependency restrictions, this will fail again, so I suggest an import based on the pymatgen
version.
Pinning the pymatgen
version is also not a good idea for this reason. I think if everyone starts pinning their pymatgen
versions we're going to run into dependency resolution conflicts.
Thanks @mbercx, I think I have to not pinning pymatgen
, but this means if they change the API in the future again, things break.
In the latest abipy version the import has been updated to fix this:
Yes, @gmatteo told me so. I'll close this.
Thanks @mbercx, I think I have to not pinning pymatgen, but this means if they change the API in the future again, things break.
Yeah, I know... But if we pin it every package that uses it in the common workflows will have to pin it to the same version, else we can't install aiida-common-workflows
at all. We could define a range and update the upper limit from time to time?
Install the package directly will install
pymatgen==2023.7.14
since the version is not pinned.I got: