Closed ondracka closed 3 years ago
Thanks for the report. We have not yet looked at 3.9. Our official support is for 3.7. We have good experiences with 3.8 as well.
We will look into this. In the mean time, we recommend using pyenv to use 3.7.
Right, how about some improvements to the howto than (how to force a specific python version with the virtualenv), because I did the pyenv setup as suggested at: https://nomad-lab.eu/prod/rae/docs/developers.html#
pip install virtualenv
virtualenv -p `which python3` .pyenv
source .pyenv/bin/activate
and still somehow ended with the python 3.9?
I feel you. I get confused using pyenv myself. The bottom line is that -p
needs to get the path to the python binary you actually want to use. We can try to add a command sequence for pyenv users to the documentation.
We resolved the mentioned python 3.9 issue. It was caused by an outdated dependency forcing installation of an outdated pydantic version. The fix will be part of the next NOMAD patch release (0.10.3).
Some quick googling suggests this is a python 3.9 compatibility issue?