-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix used-before-assignment
for assignment expressions in lambda
#5530
Fix used-before-assignment
for assignment expressions in lambda
#5530
Conversation
Pull Request Test Coverage Report for Build 1606114780
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a pattern of simply removing code and fixing bug, hmm. 🤔
Also closes #3877. Adding it to the list of closed issues. |
Do you want another review before merging ? |
I think this should be fine. We have two separate issues reports about this and this fixes this issue. I don't think this was an intended message. |
doc/whatsnew/<current release.rst>
.Type of Changes
Description
This closes #5360, closes #3877
See a prior discussion in #5241 (comment) and @jacobtylerwalls's comments about it #5241 (comment).
This also fixes the message that gets raised in
home-assistant
https://github.com/home-assistant/core/blob/296b73874054eec31d91f0db1b9a625ad5d47c32/homeassistant/components/sht31/sensor.py#L63. That also seems to indicate to me that this code is not doing anything meaningful.The original commit that added it was 5193b7d.
The tests added in that commit still pass with the change in this PR so I think this should be fine?