Danny Yang
Danny Yang
I've removed the module name prefix, so now it should only show the immediately enclosing class + the function's name.
So to summarize (whenever I have some time to get back to this): - show nested classes/methods - don't show `__unknown__` for unknown module paths
Perhaps a good next step is to get the LSP trace logs for the repro in both zed & VsCode, and compare them to see if there's a request that...
@trevor-inflection I'm curious about the `(int, int) -> int` and `() -> Generator[Scope, None, None]` - this isn't legal syntax for a regular type annotation, since PEP 677 was rejected....
I looked into this more & found a section in PEP 484 on type comments: https://peps.python.org/pep-0484/#type-comments along with the implementation code for Mypy. Thanks @trevor-inflection for the [link](https://peps.python.org/pep-0484/#suggested-syntax-for-python-2-7-and-straddling-code) re: function...
Re: sentry, they just dropped 3.6 support last month, so I assume we'll have a version of the SDK with proper type annotations soon? There's a tracking issue here https://github.com/getsentry/sentry-python/issues/5008
https://github.com/pnuckowski/aioresponses/pull/277
I've changed my mind on this issue, I think matching basedpyright here makes sense to avoid giving large numbers of false-positives on code that uses this (anti) pattern
Yes I've noticed non-deterministic results from various tests recently as well.
another report https://www.reddit.com/r/vibecoding/comments/1pbtzlg/antigravity_high_memory_problem_with_pyrefly/