[issue33048] macOS job broken on Travis CI

Carol Willing added the comment: 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. -- resolution: -> fixed stage: patch

[issue33048] macOS job broken on Travis CI

Ned Deily added the comment: Thanks, Carol! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue33048] macOS job broken on Travis CI

Carol Willing added the comment: 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. -- nosy: +willingc ___

[issue33048] macOS job broken on Travis CI

Change by Carol Willing : -- keywords: +patch pull_requests: +5847 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue33048] macOS job broken on Travis CI

Antoine Pitrou added the comment: 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. -

[issue33048] macOS job broken on Travis CI

Ned Deily added the comment: > 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 o

[issue33048] macOS job broken on Travis CI

New submission from Antoine Pitrou : 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