Repository navigation
ModuleNotFoundError: No module named 'pkg_resources' after loading scitools and um_tools #685
Alice Miller (alice-miller)
started this conversation in
Mule
Replies: 2 comments
|
It may be worth noting that works as expected. |
0 replies
|
Hi Alice, this is because we haven't previously setup the um_tools modules with the dated default scitools modules, which means the um_tools module falls back to the system python install. I guess this is mainly because no one has asked for it before! I've just updated the 2026.10.1 release with the should now work on spice/exab/excd |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When loading a specific version of scitools followed by um_tools, when attempting to run Mule I get the following error:
returns the error message:
Not specifying a scitools version (i.e. running
module load scitools) does not cause any issues. It seems that for some reason specifying the scitools version causesmodule load um_toolsto use Python 3.9 rather than Python 3.12.Removing the scitools version or specifying the correct um_tools python path manually solves the problem:
The problem occurs on the VDI and on SPICE (not tested on the HPC). Is this expected behaviour?
All reactions