On 21/08/2023 00:30, Christian Huitema via mbed-tls wrote:
On 8/20/2023 3:23 PM, Christian Huitema via mbed-tls wrote:
[snip]
I tried to solve that by installing that module using "pip", and test programs running python3 do find the "jsonschema". Calling print(jsonschema.__file__) shows the module is installed in my user directory: /users/christianhuitema/Library/python3.9/lib/python/...
Is there a simple way to fix that?
Found it. Instead of running "python3 -m pip install jsonschema" I should run "python3.10 -m pip install jsonschema". Sorry for bothering the list.
This is weird. Normally "python3 -m pip ..." is the reliable way to install python modules for our scripts since they start with "#!/usr/bin/env python3". "python3.10 -m pip ..." installs the module for Python 3.10, which may or may not be python3. (Note that each minor version of Python has its own set of installed modules.) There seems to be some inconsistency in your environment, but I don't know what it could be. Some things to check which might hint at what's wrong:
python3 --version type python3 python3 -m pip --version echo $PYTHONPATH python3 -c 'import sys; print(sys.path)' python3 -m pip show jsonschema
(If you need further help, you need python experts, or perhaps expert on whichever packaging system(s) you used to install extra python versions, not mbedtls experts.)
Best regards,