aws/aws-iot-device-sdk-python-v2

ModuleNotFoundError: No module named 'rich' when run ./start.sh

a523 opened this issue · 3 comments

a523 commented

Describe the bug

https://ap-east-1.console.aws.amazon.com/iot/home?region=ap-east-1#/connectdevice

I followed this to connect device, but run in a error,

I was using mac os . python 3.11

➜   ./start.sh                                           
Running pub/sub sample application...
Traceback (most recent call last):
  File "/Users/xxx/Downloads/connect_device_package/aws-iot-device-sdk-python-v2/samples/pubsub.py", line 10, in <module>
    from utils.command_line_utils import CommandLineUtils
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/qsas-0.1.0-py3.11.egg/utils/__init__.py", line 6, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/qsas-0.1.0-py3.11.egg/conf/__init__.py", line 7, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/qsas-0.1.0-py3.11.egg/utils/display.py", line 3, in <module>
ModuleNotFoundError: No module named 'rich'

Expected Behavior

connect succussed ,

Current Behavior

it fails reporting dependencies

Reproduction Steps

https://ap-east-1.console.aws.amazon.com/iot/home?region=ap-east-1#/connectdevice

I followed this to connect device, but run in a error,

I was using mac os . python 3.11

Possible Solution

No response

Additional Information/Context

No response

SDK version used

last

Environment details (OS name and version, etc.)

mac os

Can you try python3 -m pip install rich before running ./start.sh again?

I would also recommend trying from a fresh, clean venv. The sample's attempt to use a local module (https://github.com/aws/aws-iot-device-sdk-python-v2/blob/main/samples/utils/command_line_utils.py) is going off into some arbitrary package (qsas?)

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.