Open Andrew-S-Rosen opened 11 months ago
Please not that you most likely don't need the [parsing]
extra. Most parsers will work just fine without. The parsing extras are only required for hfd5 and netCDF based codes and some optional normalising functionality like the new SOAP descriptor.
Unfortunately, there is a limit to what we can do here. The version restrictions we removed, are already a big trade-off between easy installs and the risks of new dependency versions introducing breaking changes. For example you a couple a days ago, the pydantic 2.0.0 release was breaking our build because we removed version restriction. We removed most version restrictions on the normal install, but i am afraid we need to keep them for the extra dependencies that are most likely only affecting the service operations anyways.
@markus1978 --- thanks, that makes sense! Anyway, the more important was more about just letting you all know that the pip install
isn't working as expected, but that will presumably be resolved once the netCDF version is changed.
Of course, i just wanted to explain why we have not just removed every version restriction. We will test and see what happens if we pump the netCDF version.
I tried running
pip install nomad-lab[parsing]
and got the following error. Runningpip install nomad-lab
works just fine.Apparently,
pip install netCDF4==1.5.4
is the culprit. This is in a fresh Python 3.10 Conda environment on Ubuntu. Using a newer version of netCDF4 resolves the issue.In connection with https://github.com/openjournals/joss-reviews/issues/5388#issuecomment-1548824444, I thought the version pinning was reduced overall. Was there a specific need for 1.5.4 here?