Micha Reiser
Micha Reiser
> One thing I've noticed is that we do not seem to make use of the requires-python constraint from the inline metadata in the script. For example, when running the...
> I think we should always read the metadata, we need to do so in the LSP context. I don't think we can? Like, if you're checking an entire project,...
Agree, that we should pick up the script metadata in the LSP > Not sure what the CLI experience should be if you check a project that has PEP 723...
> detect this is a PEP 723 script by finding the metadata at all (easy) Are there any clients that do this today?
emacs is a notable client but I don't see why we should wait for all other major clients to implement script support, just so that we can provide great experience...
Hi. I'm sorry you're running into this and thanks for sharing all the logs. They're very helfpul. Can you double check what interpreter you've selected in VS Code and if...
No worries. I'm glad you figured it out and thanks for letting us know that it's now working. Happy holidays
I think the issue here is that we don't fully support system Python installations Related to https://github.com/astral-sh/ty/issues/2068
I see, so this is about changes not being detected in your system Python installation. I'll move the issue to the ty repository. Is the issue only that changes in...
@carljm the example in this issue now reveals `int` everywhere. Is there something more we want to do beyond the `typing.TypeGuard` PR or can we close it?