Raphael Gaschignard 3d0bdb426a [red-knot] Use the right scope when considering class bases (#13766) ...

Summary
---------

PEP 695 Generics introduce a scope inside a class statement's arguments
and keywords.

```
class C[T](A[T]):  # the T in A[T] is not from the global scope but from a type-param-specfic scope
   ...
```

When doing inference on the class bases, we currently have been doing
base class expression lookups in the global scope. Not an issue without
generics (since a scope is only created when generics are present).

This change instead makes sure to stop the global scope inference from
going into expressions within this sub-scope. Since there is a separate
scope, `check_file` and friends will trigger inference on these
expressions still.

Another change as a part of this is making sure that `ClassType` looks
up its bases in the right scope.

Test Plan
----------
`cargo test --package red_knot_python_semantic generics` will run the
markdown test that previously would panic due to scope lookup issues

---------

Co-authored-by: Micha Reiser <micha@reiser.io>
Co-authored-by: Carl Meyer <carl@astral.sh>

2024-10-17 22:29:46 +00:00

..

resources

[red-knot] Use the right scope when considering class bases (#13766)

2024-10-17 22:29:46 +00:00

src

[red-knot] Use the right scope when considering class bases (#13766)

2024-10-17 22:29:46 +00:00

tests

[red-knot] document test framework (#13695)

2024-10-10 12:02:01 -07:00

build.rs

[red-knot] Add a build.rs file to red_knot_python_semantic, and document pitfalls of using rstest in combination with mdtest (#13747)

2024-10-14 13:02:03 +01:00

Cargo.toml

[red knot] Use memmem::find instead of custom version (#13750)

2024-10-14 15:17:19 +02:00