Micha Reiser

Thanks again for your work. I close this PR because it's unlikely that we start working on this feature anytime soon (or review it). But we will pick it back...

Ruff should suggest you two violations for your code example if you have both UP032 and G001 enabled ([playground](https://play.ruff.rs/3cb1e0a7-44fa-445f-90f7-38c4f0ed3de4)) ```python logger.info("Result received: {}".format(result)) ``` 1. that the there's a `str.format`...

> Perhaps it would be enough if UP032 checks for a logging context, and if found, offers the solution from G004 instead? That would be possible but we prefer to...

Maybe I'm overly strict here. @AlexWaygood what's your take on whether we should make `UP032` logger aware (but only if `G004` is enabled?)

I looked at how we detect logging calls, and the implementation is prone to false positives because of Ruff's lack of multifile analysis (we're working on it). Ignoring `UP032` in...

Hi @rohanbalkondekar I'm sorry that you're running into this. Would you mind sharing the ruff extension logs with us? > If you encounter any issues with the extension or the...

@dcreager is this complete now?

Depends on https://github.com/astral-sh/ruff/pull/13563

Some extra notes from my conversation with @carljm the other day regarding on how this should be implemented > In general, when we query the type of a symbol from...

Possibly related https://github.com/astral-sh/ruff/issues/11907