Add support for ty

[TheLocehiliosan]

Name: ty
URL: https://github.com/astral-sh/ty & https://docs.astral.sh/ty/features/language-server/

Newly announced python type checker / language server from Astral.

w0rp Edit

See also: astral-sh/ty#301

Let's encourage them to implement pull diagnostics like Pyright does!

[w0rp]

You beat me to it. 😃 See my edit.

[bugant]

@w0rp it seems that pull diagnostics is supported by ty. Any help needed here?

[TheLocehiliosan]

Any update on this? I see that recently the ty project removed the preview warning from their README. They might be ramping up to do a non-alpha release.

[TheLocehiliosan]

ty is now in beta and recommended for production use.

https://astral.sh/blog/ty

[spaceone]

@TheLocehiliosan I have a working ty linter in #5078

[jcocozza]

I've been trying to get the LSP working (ty server command).

I've managed to get some of the "on demand" commands like ALEGoToDefinition and ALEHover working, but I haven't been able to get it to report errors that should be reported (e.g. realtime linting).

My understanding is that since ty implements pull diagnostics, ALE should "just work" and while you're typing, error messages should appear. Is this wrong?

I have a couple of guesses as to why it isn't working:

• I've somehow horribly mis-configured something (although gopls works out of the box for me and I modeled the ty lsp file after that)
• There is additional work beyond the ale_linters/python/ty.vim file that needs to be done for lsp's to report diagnostics properly.
• ty check only works with files on disk (no reading from stdin), so maybe there are similar issues with the ty server command. Although saving the file doesn't seem to make a difference for me.

If anyone has ideas I'd like to hear them.