Jack O'Connor 5f2e855c29 allow reads of "free" variables to refer to a global declaration ... Previously this worked if there was also a binding in the same scope as the `global` declaration (probably almost always the case), but CPython doesn't require this. This change surfaced an error in an existing test, where a global variable was only ever declared and bound using the `global` keyword, and never mentioned explicitly in the global scope. @AlexWaygood suggested we probably want to keep that requirement, so I'm adding an a new test for that on top of fixing the failing test.		2025-07-16 08:30:42 -07:00
..
resources	allow reads of "free" variables to refer to a global declaration	2025-07-16 08:30:42 -07:00
src	allow reads of "free" variables to refer to a global declaration	2025-07-16 08:30:42 -07:00
tests	Auto-generate environment variable references for ty (#19205)	2025-07-08 10:48:31 -04:00
build.rs	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00
Cargo.toml	[ty] Remove countme from salsa-structs (#19257)	2025-07-10 11:45:09 +00:00
mdtest.py	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00
mdtest.py.lock	Rename Red Knot (#17820)	2025-05-03 19:49:15 +02:00