# Dropping Intel Mac to Tier 2

**URL:** <https://discuss.python.org/t/dropping-intel-mac-to-tier-2/102100>\
**Category:** Core Development\
**Created:** [August 12, 2025, 11:01am UTC](https://discuss.python.org/t/dropping-intel-mac-to-tier-2/102100 "2025-08-12T11:01:44Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [August 12, 2025, 11:01am UTC](https://discuss.python.org/t/dropping-intel-mac-to-tier-2/102100/1 "2025-08-12T11:01:44Z")

</div>

Hello,  
As @webknjaz [reported](https://github.com/python/cpython/issues/137638), GitHub will be [dropping](https://github.blog/changelog/2025-07-11-upcoming-changes-to-macos-hosted-runners-macos-latest-migration-and-xcode-support-policy-updates/#macos-13-is-closing-down) their last Intel Mac image. Brownouts will begin September 1, so we need to make the job non-blocking by then.  
Cirrus and Circle CI already dropped Intel Mac.

This means that we’ll likely need to move Intel Mac to Tier 2 in [PEP 11](https://peps.python.org/pep-0011/).  
Another option would be to run the tests with Rosetta, but setting that up would probably be too much work for the benefit.  
See [the issue](https://github.com/python/cpython/issues/137638) for more details.

What makes me a bit worried is that Tier 2 requires 2 core dev contacts. How many core devs still use an Intel Mac?  
We do have buildbots, thanks to Matt Billenstein and @itamaro.

---

_[View the full topic](https://discuss.python.org/t/dropping-intel-mac-to-tier-2/102100)._