James Addison

@jayaddison > > Do we need to update `ENV_VERSION` with this change? @AA-Turner > We shouldn't need to, as the resulting data that gets stored in the environment is unchanged...

I'm cautiously in favour of doing this, but perhaps we should delay for a while (a month?) to ensure that any further 7.3.0 issues are tracked down before doing something...

> > Also a question that I couldn't find a clear answer to: is there a standard way to annotate package metadata to say what (if any) Python code formatter...

Perhaps with 8.0.0 released and apparently fairly stable (I haven't seen many bugreports - anyone else?), perhaps it's a good time to consider autoformatting again?

I suppose I see as a bit like a breaking change: it's disruptive for developers (although in this case, primarily internal developers -- as compared to API-breaking changes, which affect...

(it's _probably_ a bad idea anyway -- especially if it messes up a significant number of comments and/or code blocks)

> TL;DR: Usage is > > ``` > app.stderr(flavor='re').assert_match('.*my message') > ``` Checking some of the design reasoning for the method signature: * A reason to prefer the caller to...

> I think `assert_match(expect, flavor=...)` is more natural but I'm open to suggestions. I think I'd probably prefer a developer experience of: * `assert_contains(string)` to check for lines containing `string`....

@AA-Turner is it OK if we pause on this one for a while? I think/hope it's a good idea, but I'm slightly concerned that the distinction between lenient and strict...

Another way to phrase that: I'd like to canvas more (and perhaps leaning skeptical) opinions about this before proceeding.