Hi,
I tried following the install instructions helpfully included in your top-level README.md.
Currently, anaconda3 will install python 3.12.3, and it seems like some of the code is not happy with some of the changes in python3.12 ...
(kcap_env) dlang@mn003:~/kcap$ cosmosis runs/config/KV450_no_sys.ini
Traceback (most recent call last):
File "/home/dlang/.conda/envs/kcap_env/bin/cosmosis", line 2, in <module>
import cosmosis_main
File "/home/dlang/.conda/envs/kcap_env/bin/cosmosis_main.py", line 5, in <module>
from future import standard_library
File "/home/dlang/.conda/envs/kcap_env/lib/python3.12/site-packages/future/standard_library/__init__.py", line 65, in <module>
import imp
ModuleNotFoundError: No module named 'imp'
I understand that's not a problem in the kcap code itself, but it seems like maybe the future package is not as future proof as one might hope...
Maybe you want to pin the python version in the conda_env.yaml file?
Hi,
I tried following the install instructions helpfully included in your top-level README.md.
Currently, anaconda3 will install python 3.12.3, and it seems like some of the code is not happy with some of the changes in python3.12 ...
I understand that's not a problem in the
kcapcode itself, but it seems like maybe thefuturepackage is not as future proof as one might hope...Maybe you want to pin the python version in the
conda_env.yamlfile?