pylyzer VS ruff

There's pylyzer[0], but it's in the early stages.

[0] https://github.com/mtshiba/pylyzer

I’ve just found out pylyzer https://github.com/mtshiba/pylyzer

Not sure how good it is.

That explains why I didn't see textDocument/semanticTokens/full or anything like it in pyright's code. Do you happen to know of any Python LSP that has semantic tokens? pylsp, pyright, and jedi-language-server all don't have it. The only one I could find that might support it is https://github.com/mtshiba/pylyzer but I haven't tried that LSP yet

You might want to check Pylyzer then (https://github.com/mtshiba/pylyzer).

I'm not involved at all. It is still very very early in development. But as it is in the same vein, I thought I'd mentioned it here.

I don't need a lot. Something like "go to definition" and "show docstring" would go a long way, "signature help" would be nice... I'd take a nice completion, but that would just be a cherry on top. Any low-effort ways to achieve this? I've found https://github.com/mtshiba/pylyzer which looked really nice (and I could just download the right binary), but it has another programming language as a dependency, which is kind of intimidating...

Perhaps pylyzer can deliver. https://github.com/mtshiba/pylyzer

Ruff is an open-source Python linter created by Astral Sh that stands out for its impressive speed, adaptability, and wide-ranging features.

Leverage Python Tools: Tapyr takes advantage of Python’s ecosystem tools, including ruff, pytest, and others.

I think I mention this all the time when this comes up, but I learned the most 'best practices' through using ruff.

https://docs.astral.sh/ruff/

I just installed and enabled all the rules by setting

Ruff is a Python linter that helps to identify and remove code smells. Over 700 built-in rules: Ruff includes native re-implementations of popular Flake8 plugins, like flake8-bugbear. And also built-in caching to avoid re-analyzing unchanged files.

Because the Python's "ast" modules is too slow, and lacks proper "format" feature (it has unparse but it removes comments, and forgets the current style completely). I use "ruff" a lot (https://github.com/astral-sh/ruff) which is in Rust. But I want to be able to implement fast custom linters in Go (linters that ruff / fixit lack, and Python linters lack or are too slow).

I think it’s interesting that rye uses ruff (https://github.com/astral-sh/ruff) for linting and formatting. That’s the right call, and it’s also correct to bundle that in for an integrated dev experience.

I had to guess, that’s the path that the Astral team would take as well - expand ruff’s capabilities so it can do everything a Python developer needs. So the vision that Armin is describing here might be achieved by ruff eventually. They’d have an advantage that they’re not a single person maintenance team, but the disadvantage of needing to show a return to their investors.

Adding more weight to ease of setup and configurability, the choice came down on flake8. It is easy to integrate, since its also available through pip and let’s you configure which standards you want to omit by simply stating them as a list via the --ignore switch. Moving to ruff appears quite smooth, so future updates may do so.

I confess I stole the pip recipe from Charlie :D

https://github.com/astral-sh/ruff/blob/main/.github/workflow...