Hi, following the iot hub _quickstart-send-telemetry-python_ example I'm having the following problem when launching the SimulatedDevice.py:
'Traceback (most recent call last):
File "SimulatedDevice.py", line 11, in <module>
import iothub_client
File "C:\Users\Utente\AppData\Local\Programs\Python\Python37\lib\site-packages\iothub_client__init__.py", line 1, in <module>
from .iothub_client import *
ImportError: DLL load failed: The specified module could not be found.'
python version 3.7.0 AMD 64
Package | Version
azure-iothub-device-client | 1.4.3
iothub-client | 1.1.2.0
pip | 18.0
setuptools | 39.0.1
The same happens debugging from VS Code
I'm certainly missing something, but I can't fix it
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@MarcoStucchi Thank you for the feedback! We are investigating this and will get back to you shortly.
Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.
Hi @MarcoStucchi - I believe this is an issue with the SDK - please see: https://github.com/Azure/azure-iot-sdk-python/issues/205
Can you confirm that you see the same error if you try this sample: https://github.com/Azure/azure-iot-sdk-python/blob/master/device/samples/iothub_client_sample.py
Thanks, Dominic
Hi @dominicbetts - the suggested SDK sample returns the very same error.
I've read the https://github.com/Azure/azure-iot-sdk-python/issues/205 and the issue is clear. I've tried node samples with more success. Does this tell something about language of choice when approaching Azure programming ? Is Python a valid choice or does it come last in Microsoft order of precedence ?
Thank you, Marco
Hi @MarcoStucchi - did you see the workaround suggested in https://github.com/Azure/azure-iot-sdk-python/issues/205 ?
As this is issue is being handled in the https://github.com/Azure/azure-iot-sdk-python repo, I'm going to request that this issue is closed. Please feel free to reopen it if you have any further documentation related questions. Thanks again.
Hello @MarcoStucchi,
Azure IoT SDKs are supported in 5 different languages. The effort is to enable all Service and Device side features on all different languages. Since we depend on many other open sourced SDKs sometimes we can achieve a feature first in one language and then on others. All work is transparent on the SDKs and you can track what is blocking a specific feature by looking at the open issues. Anyone can contribute to the SDKs and help us achieve a feature faster :)!
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
@MarcoStucchi
I've tried node samples with more success. Does this tell something about language of choice when approaching Azure programming ? Is Python a valid choice or does it come last in Microsoft order of precedence ?
just wanted to chime in (late) on this particular comment: I totally understand the sentiment and this is definitely not what we want to convey. Choices were made early in the Python SDK development that were based on our understanding of where the industry was 2-3 years ago and these choices have not stood the test of time. Hopefully, you'll be glad to hear that the same team that worked on the Node SDK is taking care of rewriting a full "native/modern" Python SDK that does not rely on C wrappers or external C dependencies like Boost. we're on it - we'll fix it. Hopefully, it's won't be "too little too late".
Hi @pierreca, @sergaz-msft : any idea when the full "native/modern" Python SDK will be available, or if it's in preview?
thanks
@dhtoran it's not in preview yet but the work is in progress and we should have a first preview that includes C2D and D2C (not twins & methods yet) by mid-february. we're still busy stabilizing the fundamentals (state machines, async APIs etc. Once we get all that done, we'll ramp up features quickly.
@pierreca any progress on this?
Most helpful comment
@dhtoran it's not in preview yet but the work is in progress and we should have a first preview that includes C2D and D2C (not twins & methods yet) by mid-february. we're still busy stabilizing the fundamentals (state machines, async APIs etc. Once we get all that done, we'll ramp up features quickly.