Micha Reiser
Micha Reiser
> (and making them opt-out makes most sense IMHO) which they already are. Or more specifically, you can opt-out of the syntax errors by using [`per-file-target-version`](https://docs.astral.sh/ruff/settings/#per-file-target-version) and setting it to...
I'd prefer an option to either disable this behavior or changing the syntax version per file over making syntax errors suppressable
We've only had very few reports and some of them were related to bugs in the parser. It's also easier to have a single config flag than to configure a...
> I think we can fix this if we keep the diagnostic for removing end-of-line comments but make the fix unsafe, but suppress the diagnostic for comments like the ones...
Related: https://github.com/astral-sh/ruff/issues/4464
Supporting `.python-version` as a fallback does make sense for applications when neither `target-version` or `project.requires-python` is specified. But I'm still somewhat hesitant to add this because it does mean that...
You could but it seems to be sort of an anti-pattern. See the conversation in https://github.com/astral-sh/uv/issues/11624#issuecomment-2669110520
Thanks for working on this. For an initial version, I suggest focusing on just rendering the `concise` diagnostic message without any subdiagnostics. The main reason is that I don't want...
Thank you for your work on feature. Almost the entire team is out this week. It may take a few days before someone finds time to review your PR. Happy...