John Litborn

> I think we have a rule for detecting and deleting empty type-checking blocks specifically, but we could make this part of the fix for the general "delete statement" logic....

> Hi [@jakkdl](https://github.com/jakkdl), thanks for the patience. Could you please provide your use case and also how you are implementing or reproducing this? Also, please add boto3.set_stream_logger('') for logs too....

With the simplification from removing Any-tuple this looks pretty damn clean. With no diff from mypy_primer I think we only need new tests and then it's pretty much ready to...

Would be lovely to get this merged, but it appears we've gotten merge conflicts that need resolved @A5rocks

This seems quite doable (and I'm up for writing PRs to do so), the Pyre Query API is considered legacy code - so replacing that with interfacing with `pyre persistent`...

Okay, after looking into this quite a bit ... it unfortunately seems like it's not really possible with the given LSP features supported by mypy & pyre 1. https://github.com/python-lsp/pylsp-mypy seems...

> AFAIK our best bet is to use a hover lsp request at least for pyre, have you tried that? Looks like this gives some type info for some symbols,...

Randomly found https://github.com/python/mypy/blob/cfec71798175fcbf030d6d114750d6fac454b3c9/misc/find_type.py which works by copying the current file to a temp file, shoving in a line with a `reveal_type`, and running `mypy` on it. Very elegant :sweat_smile: Somewhat...

Okay, LSP is out of the question then. So if we still want the functionality, the alternatives as far as I can tell are: #### `mypy` 1. Write a visitor...

I'm making solid progress on this, but pytest-anyio does not support clocks/instruments (https://github.com/agronholm/anyio/issues/260), so will have to add that functionality