Micha Reiser

Okay, I'm done with the rebase and I very much hope I didn't mess anything up. I now need to get a better understanding of the change itself to be...

I'm trying to get my head around over all the changes and are having a hard time. What's unclear to me is: * What's the exact mapping from old rules...

From the chanegelog: `Added asyncio support for several error codes`. I think that' the case for most of the TRIO rules. This isn't something we have to change as part...

Okay, I think I now have a good overview of what has changed. I plan on reviewing this PR tomorrow (and hopefully merge). I don't think there's anything we can...

@jakkdl Thanks for detailing the upstream features. I mainly tried to document with *no support* what features Ruff lacks compared to the upstream rules. I don't think we should or...

I manually tested the redirection rules and it all looks good. Let's merge this.

I think one nice follow up after the release would be to rename the rules to match the upstream names.

Disabling fixes for token-based rules makse sense to me, unless we have a way to know whether a token range overlaps with a parser error range. Long term, I think...

@jaraco any chance you're building inside of WSL? I'm asking because I'm surprised that it tries to build `x86_64-pc-windows-gnu` instead of the msvc target.

Oh, that's interesting and not something I have thought of when implementing suppression comments. > `# fmt: skip` comments suppress formatting for a preceding statement, case header, decorator, function definition,...