Alex Lowe

One possible implementation of baselines that would handle many of the issues herein (though it would introduce at least one of its own) would be to incorporate the baseline into...

Not really sure... Naively, it appears to me that the most consistent way to configure it would be to have `warn` and `extend-warn` (or `warning` & `extend-warning`). [This file](https://github.com/canonical/craft-parts/pull/337/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711) contains...

@jfmengels while what you mention would be ideal, I don't believe it's practical for ruff. ### Disable comments Let's take for example a project that has its own [`Formatter`](https://docs.python.org/3/library/logging.html?highlight=logging#logging.Formatter) subclass...

Just adding my voice to agree with this. It appears that most people are either in favour of or indifferent to `X | Y` replacing `Union[X, Y]`, but a big...

Not based on a formal survey, just based on asking other developers what they think

What if UP007 became a way to just enable both of the split out rules + write a deprecation warning? I'm not too worried about the edge case where someone...

@DanielDewberry if you have opinions on a general case for this on more commands (e.g. `list-tracks`), I'd love to hear them in [this feature request](https://github.com/canonical/craft-application/issues/342).

@mr-cal that was a quick & dirty hack to get the project name in the PoC that made it into production accidentally. We need to pull the project name out...

@AkechiShiro it's not in mainline 6.8-rc5, so it's probably not in 6.7.

Yeah, having environment variables available for this would be very useful for us. We have two different build environments we use, and neither of them make it particularly easy to...