Erik De Bonte

Wondering if this might be related to my recent changes to add the `callable` semantic modifier. Eric had [warned us](https://github.com/microsoft/pylance-release/issues/5841#issuecomment-2091230478) that implementing that feature would require type evaluation and might...

> if this was for me, i can't access it :D Sorry, no, I was talking to @rchiodo.

Can any of you provide a code sample that reproduces this behavior?

> this code was in issue as example Here's what I tried: 1. Create a new directory 2. Create a venv 3. `pip install telethon` 4. Create `test.py` and paste...

> [@debonte](https://github.com/debonte) I was able to reproduce the issue. You can see it in my logs above. > > Essentially I copied the original poster's code, then commented and uncommented...

Might be a difference in our settings? I'm on defaults for everything except that `typeCheckingMode` is set to `standard`.

This issue has been fixed in prerelease version 2025.5.101, which we've just released. You can find the changelog here: [CHANGELOG.md](https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#20255101-3-June-2025-PreRelease)

> Awesome to have syntax highlighting for PEP 695 type aliases. However, type parameter are still missing unfortunately. Thanks for pointing that out. I opened https://github.com/microsoft/pylance-release/issues/6942 to track that.

Transferring to Pyright as I'm not sure if this is expected behavior. We will report a `reportPossiblyUnboundVariable` diagnostic if you set `python.analysis.typeCheckingMode` to `standard` or `strict`. Or alternatively you could...

@sminnee, are you wanting this to be fixed in Pylance or is the primary issue that you want to configure `pyright-python` to use pyright 1.1.402?