Micha Reiser

@Winand whether you want to open a new issue depends on your goal: * if you want help, please open a new issue. * if you don't need help and...

You can use [`per-file-target-version`](https://docs.astral.sh/ruff/settings/#per-file-target-version) or `extend` with `target-version`

Ruff doesn't support multifile analysis yet but we're working towards bringing this capability to Ruff. But it will take a while and we then also have to change this specific...

yeah, we could consider adding an option or splitting the `__init__.py` behavior into its own rule.

@adamh-oai is there a high likelihood that each pull changes some pyproject.toml? > Both this and the 50-copies-of-rg issue sort of feel like VSCode is triggering a whole bunch of...

@dhruvmanila I wonder if it's time to change our settings discovery to be lazy instead of doing it eagerly. It would not only help with the single file case but...

We plan on releasing a new patch version tomorrow

I'm not familiar with the language model tool API but I'm a bit surprised that it's necessary to expose information that's already exposed by generic language server options. I read...

This is an interesting case because it shows that there's a cycle: * `__init__.py` depends on `_private.py` to know the type of `PublicClass` * `PublicClass` (`_private.py`) depends on `__init__.py` to...

We would need to extend our release matrix here https://github.com/astral-sh/ruff-vscode/blob/6ac401c6474f0acfa2d28a04aeef7ca6b4261af5/.github/workflows/release.yaml#L48-L52 and add a PPC64 build for both VS code and the VSX marketplace