3 ms·
From my looking around, Homebrew's Python 3.11 has specific binaries for each macOS and CPU architecture https://github.com/Homebrew/homebrew-core/blob/c1321e2
by shpx 3y ago
From my looking around, Homebrew's Python 3.11 has specific binaries for each macOS and CPU architecture
https://github.com/Homebrew/homebrew-core/blob/c1321e262920354d26cb758b2f5fd3c2ac946ca7/Formula/p/python%403.11.rb#L14-L22 https://github.com/Homebrew/homebrew-core/blob/c1321e2629203...
A comment in Homebrew's formula says that Homebrew adds the --enable-optimizations flag during compilation because Homebrew has separate binaries whereas the official Python release doesn't add this flag because "they want one build that will work across many macOS releases"
https://github.com/Homebrew/homebrew-core/blob/c1321e262920354d26cb758b2f5fd3c2ac946ca7/Formula/p/python%403.11.rb#L141-L145 https://github.com/Homebrew/homebrew-core/blob/c1321e2629203...
and it looks to me that pyenv just installs the official binary
https://github.com/pyenv/pyenv/blob/28e7000b485bff61235d8a691c3989c9a5ed0a53/plugins/python-build/share/python-build/3.11.5#L7 https://github.com/pyenv/pyenv/blob/28e7000b485bff61235d8a69...
So I would expect it to be the other way around, Homebrew's Python should be faster.