Thanks!

I don't know much about homebrew -- would it be worth adding the other two environment variables that were just added to CPython's workflow in https://github.com/python/cpython/pull/102074/files as well?

I don't know much about homebrew -- would it be worth adding the other two environment variables that were just added to CPython's workflow in python/cpython#102074 (files) as well?

Me neither, but here's the doc: https://docs.brew.sh/Manpage#environment
HOMEBREW_NO_AUTO_UPDATE definitely. For the same reasons we don't need to update pip in the CI
HOMEBREW_NO_ANALYTICS is up to you I guess. Analytics is good for the homebrew devs. I think it's more a matter of opting out of data collection than speeding up CI (although anything that speeds up CI isn't bad either): https://docs.brew.sh/Analytics#opting-out

HOMEBREW_NO_ANALYTICS is up to you I guess. Analytics is good for the homebrew devs. I think it's more a matter of opting out of data collection than speeding up CI (although anything that speeds up CI isn't bad either): https://docs.brew.sh/Analytics#opting-out

Running stubtest on macOS in CI is consistently slowesr/more backed-up than the other two operating systems, so I'd be up for it tbh :p

Also, same as CPython (python/cpython#102074 (comment)), we're probably somewhat atypical users of homebrew 😄