-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initialization error? #69
Comments
@yeyeto2788 I read this a couple of days ago, interesting, I will look into this during the weekend, hopefully :) I am doing some other stuff, Also I wanted to test the other issue, so maybe I can do both at the same time but no promises, :) |
@yeyeto2788 Do you have a solution in mind, maybe some brainstorming in Discord? let me know. Thanks :) |
Sure, sorry for the late reply. My suggestion would be to actually either raise the error so anyone can handle it as one wants (My preferred option) or by just now raising the error but not instantiating any object. If you want to discuss it further do not hesitate on sending me a DM on Discord. |
No problem, wlil do. Thanks |
Please take a look at the following snippet (explanation after it):
Expected behavior:
Could not instantiate the DHT object as when setting the
use_pluseio
toFalse
so behavior is the same and instantiation can be handled the same way.Issue/Doubt:
Shouldn't the library raise an
Exception
when (by default)use_pulseio
is set toTrue
instead of actually instantiate the DHT11 object?SBC: Raspberry Pi A+
Libraries:
Python: 3.7.3
The text was updated successfully, but these errors were encountered: