Micha Reiser

> I think you're right that we should support `nosec` comments. It's similar to our support for isort's comment directives. I do see value in supporting `nosec` suppression comments to...

@leonardder, thank you for your interest. My understanding from the original issue is that it is mainly about the ability to configure the preferred indentation in the formatter, and this...

> Long story short, if the auto formatter is able to present us this code style without remaining linter warnings, we'd be able to switch: You won't need to use...

Are you planning to use these rules alongside the mccabe complexity rule or instead of it?

> I do run McCabe in Ruff as well, but they serve three different purposes, IMHO. Could you explain how the purpose between Mc Cabe and this rule differ in...

Thanks, that makes sense. What's the motivation for catching the switch if it is easy to understand? I'm asking because we're currently leaning towards having one single complexity rule with...

Note: We should clarify whether the `length` means number of characters or the unicode width. Or are unicode names not supported by python (whether they're discouraged is another question ;))

Having a dedicated `output` (or `output-file`) option has precedence in * ESLint (`output-file` | `-o`) * `dotnet format --report` * Jest (`--outputFile`) in combination with `--json`

CC: @dhruvmanila

The issue is probably more general and applies to all python versions that are on the PATH. See [this comment](https://github.com/astral-sh/uv/pull/940#issuecomment-1949127576)