Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

62%
+3 −1
Q&A What's causing mypy to give an `[assignment]` error in this nested for loop?

As the error message indicates, the assignment is to the variable row. The for loop will repeatedly assign to row. But why is there a problem? Because Python's scoping rules are bad/broken. There ...

posted 1y ago by Derek Elkins‭

Answer
#1: Initial revision by user avatar Derek Elkins‭ · 2022-12-28T01:36:52Z (over 1 year ago)
As the error message indicates, the assignment is to the variable `row`. The `for` loop will repeatedly assign to `row`.

But why is there a problem? Because Python's scoping rules are bad/broken. There is no block scoping. The scope of any variable within a function is that entire function except for the bodies of nested functions. The scope of the iterating variable in a `for` loop is not just the `for` loop. The scope of variables within a block, e.g. within the body of a `for` loop, is not just that`for` loop. There is no shadowing of variables except by nested functions.

The upshot for your example is that you use `row` in two different `for` loops looping over two differently typed expressions, so `row` ends up being assigned two different types because there is only one `row` variable.

Specifically, `for row in self.diagram:` leads to `row` having type `str`, but `for row in self.seed_diagram:` would assign `row` with a value of type `list[str]`. Hence the error.

The most direct resolution would be to use a different variable name for each of these loops.