DetachHead

yeah that's what i meant sorry, updated the example to be more clear

```py class Bar: asdf: int = 1 class Foo: def __init__(self, value): self.value = value reveal_type(Foo(Bar()).value) # Bar ``` introduced in d29087520b652ed9368fa84c04cf3b107ed99b93

alternatively if we decide not to support #293 as a use case of baselining, perhaps this shouldn't appear if the baseline file doesn't already contain any errors of that type,...

dont think so, this issue seems to have been introduced in the latest release

workaround: use new type alias syntax ```py from typing import Annotated type F[T] = Annotated[T, 1] # no error a: F[int] = 1 ```

it also reports `valid-type` with th following message: ``` Type parameters for "FunctionType" requires __future__.annotations or quoted types ``` even when `__future__.annotations` is imported

it should also narrow in cases like this: ```py from typing import Literal value: str assert value == "asdf" # not sure about this because __eq__ can be overridden assert...

fyi in case anyone was confused and thought this feature was removed in black version 24.1 like i did, the string processing now has to be enabled with `--enable-unstable-feature=string_processing` in...

it's a corporate environment with custom internal certificates that need to be known about by the libraries the project uses. it's much easier to just commit the certificate than getting...

it might also be worth noting that my team uses [pyprojectx](https://pyprojectx.github.io/) to manage the uv installation locally in our project instead of installing it globally. we prefer to minimize the...