Pylint: E1133:not-an-iterable on query result #3671
Replies: 4 comments 1 reply
-
Debugging I figured out it gets down to here and gets ... except none of Lines 1073 to 1083 in 81531e8 |
Beta Was this translation helpful? Give feedback.
-
Always. It's been one of those things where I see it while I'm in the middle of something else, go "I really should make a note of that but I'm busy right now", and then forget once I'm done with the code I'm writing. It's been bugging me for ages now and I keep meaning to check what's what. The short (but unsatisfying) answer is "use |
Beta Was this translation helpful? Give feedback.
-
@davep well I'm glad it's not just me 😁 I did some digging prior to seeing your reply, my notes if someone else wants to pick it up: I use VSCode debug with
Then break point here: https://github.com/pylint-dev/pylint/blob/a841a7d9eab654e423a115b4feaa857d5f807c88/pylint/checkers/typecheck.py#L2291-L2294 Add disabled break point here: Hit first break, then enable second break and continue. Will hit
which causes But that's so deep in to |
Beta Was this translation helpful? Give feedback.
-
@davep we have an answer, per:
Underlying issue is: But currently unfixed and no workaround 😞 |
Beta Was this translation helpful? Give feedback.
-
Edit:
Caused by upstream bug:
Workaround is to use
results
.Can anyone replicate this?
Makes no sense because:
textual/src/textual/css/query.py
Lines 141 to 142 in 81531e8
And following though Pylint code it seems that's all it should need:
Any ideas? 🤔
Beta Was this translation helpful? Give feedback.
All reactions