terminalprogress causes thousands of iTerm2 alerts

[nedbat]

Using pytest 9.0.0 with iTerm2 3.6.5, my test suite caused thousands of alerts like this:

I understand I can disable this with -p no:terminalprogress, but it was alarming and others might not read through the detailed (thank you!) release notes. iTerm2 sets two environment variables:

ITERM_PROFILE=Main
ITERM_SESSION_ID=w0t1p0:3DB6DF06-FE11-40C3-9A66-9E10A193A632

Is it too ad-hoc to detect one of these variables and default the plugin to off?

[bluetech]

I was aware of such a possibility but I thought it was fixed in iTerm, but looks like 3.6.5 is the latest version.

I think we can start with turning it off if ITERM_SESSION_ID is set (seems better than ITERM_PROFILE). We also discussed that if we get more reports like this then we'll disable the feature by default. But maybe we can get away with only special casing iTerm.