Well, it didn't take long. The macOS job broke on Travis CI. Apparently "brew" thinks Python 2 and Python 3 are the same thing, so "brew install python3" now fails with an error message telling to use "brew upgrade" instead.  But it did work before...
https://travis-ci.org/python/cpython/jobs/352036713

This should be simple to fix, though I wonder whether this could be taken over by our macOS maintainers? :-)

> This should be simple to fix, though I wonder whether this could be taken over by our macOS maintainers? :-)

I'm not sure what you mean by *this*.  If it's the Travis configuration, I don't use Homebrew myself and I have little experience with Travis or with our current configuration.  I have seen that the Homebrew project recently changed their defaults so that "python" pointed to "python3" and, because of pushback, have changed some things (see https://docs.brew.sh/Homebrew-and-Python.html).  I also see the pre-revert of our .travis.yaml did not try to install the brew python3 (https://github.com/python/cpython/pull/3367/files).  Perhaps someone more familiar with both can take a quick look.  I'm really busy with other things right now.

I meant that the Travis macOS configuration could indeed be maintained by macOS experts, indeed.

The alternative, IMHO, would be to declare that bugs in macOS can appear without the offending PR being reverted if it was submitted by a non-macOS developer.

I've opened a WIP PR to fix the Travis test config on macOS. Antoine is correct that the recent brew changes related to Python caused the test failure.

I will try to get working on Python3 first and then Python2.

Thanks, Carol!

Folks, I'm going to close this as resolved since we are now using Azure Pipelines for MacOS as well. Brew has also since come up with a naming policy for 2 or 3 so hopefully (?) there will be no further renaming.