• Universal Build Broken Using Python 2.7.2 Dmg For Mac Download
• Universal Build Broken Using Python 2.7.2 Dmg For Mac Pro
• Universal Build Broken Using Python 2.7.2 Dmg For Mac

Replacing Mac OS X's system Python is not recommended due to incompatability with other software. However, there are Mac binaries on the that can be installed to a different location. Once installed, you may need to change your PATH environment variable so the new Python interpreter will run when python is invoked from the command line. To edit your PATH, determine the absolute folder path containing the Python binary. This may look something like /Applications/Python/./bin.

Add the following line to your /.bashprofile file: export PATH=/path/to/new/python/bin:$PATH The change will take effect after you restart your shell. 'Traceback (most recent call last): File ', line 1, in File '/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pygame/init.py', line 95, in from pygame.base import. ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pygame/base.so, 2): no suitable image found.

Did find: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pygame/base.so: no matching architecture in universal wrapper' – Jun 19 '14 at 7:18. The easiest, non-intrusive way would be to use: /usr/bin/ruby -e '$(curl -fsSL Then, read the instructions that are printed from your shell. Installing Python 3 With Homebrew you can install Python 3.x: brew install python This will put a python3 binary in /usr/local/bin, and a python binary pointing to python3 in /usr/local/opt/python/libexec/bin. You will additionally get a pip3 command for that version of Python. These formulas will not conflict or take precedence over the system packages unless you override your PATH.

That is, if you want python to refer to python3, add the following to your shell config: export PATH=/usr/local/opt/python/libexec/bin:$PATH Read the for more info. Installing Python 2.7 You can also get an up-to-date version of Python 2.7, if you require that for legacy reasons: brew install python@2 This will give you a python2 binary, and it will override the system python to use the Homebrew-built Python 2.7.

Classification: Investigate using Apple clang for building OS X installers:: resolved: Build, macOS: Python 3.7, Python 3.6, Python 2.7 process: closed: fixed::: ned.deily: abarnert, ned.deily, python-dev, r.david.murray, rhettinger, ronaldoussoren, skip.montanaro: normal: patch Created on 2013-09-14 20:31 by ned.deily, last changed 2018-04-15 20:41 by ned.deily. This issue is now closed. Pull Requests URL Status Linked Edit merged ned.deily, 2018-04-14 14:25 merged ned.deily, 2018-04-14 14:48 Messages (14) - Author: Ned Deily (ned.deily). Date: 2013-09-14 20:31 On the python-dev mailing list, Raymond Hettinger asks: I was exercising the alpha two release of 3.4 and noticed that it is still being built under GCC 4.2.1. Is there any reason we have to use an old compiler? It's because the 64-bit/32-bit installer we supply is designed to run on multiple versions of OS X: 10.6 (Snow Leopard), 10.7, 10.8, and the upcoming 10.9.

The safest way to ensure that the bits produced (executables, shared libs, and.so bundles) are linked with compatible versions of system shared libraries and frameworks is to build on the lowest supported system, 10.6, or - carefully - with a 10.6 SDK on a newer system. The standard compiler in the Apple Developer Tools for 10.6 is gcc 4.2. The most recent Developer Tools for 10.8 and 10.7 systems, Xcode 4.6.x, have a mature clang but do not provide a 10.6 SDK. Even with using an SDK, it's still possible to end up inadvertently linking with the wrong versions of system libraries. We have been burned by that in the past. I would like to see it built under the latest version of Clang (like the other tools on the Mac) or under GCC 4.8.1.

I've better using the latter for many months. It works great and produces.much. better code (in terms of readability for those of us who look at assembly output and in terms of speed (approx 20-25% better for cpu bound code)). I'm wondering whether is some issue that forces us to use GCC 4.2.1 or whether that is just an artifact of continuing to do what we've always been doing. I'd like to move to Apple's latest clang, as well. (Apple is dropping gcc totally from the next release of Xcode.) There are a couple of approaches that may work and still reliably support multiple versions of OS X.

Investigating this is on my list of things to do prior to the next alpha. Author: Skip Montanaro (skip.montanaro).

Date: 2013-09-18 17:26 If you find it difficult to find people with 10.6 systems to build a Python dmg for that platform, give me a shout. I'm not planning on replacing my system anytime soon. I have 10.6.8 installed, and what I believe to be the last Xcode version to support it, 3.2.something. Author: Ned Deily (ned.deily).

Date: 2013-09-18 17:41 Thanks, Skip. At the moment, finding platforms for building and testing is not a problem: I have at hand running versions of the latest releases for 10.3 onwards.:) (Buildbots for automated testing are another issue, though. We have a critical need for buildbots running more recent versions of OS X, though. At the moment, the only OS X buildbot is one running 10.4 (Tiger). If anyone is able to provide newer ones, please see. Or, if someone would like to donate hardware, I may be able to arrange hosting for it.) - Author: Skip Montanaro (skip.montanaro).

Date: 2013-09-18 18:50 I guess snakebite never materialized? - Author: Ned Deily (ned.deily). Date: 2013-09-18 19:05 Snakebite did provide some additional OS X buildbots for a while but, AFAIK, they have been offline for some months now. David Murray (r.david.murray). Date: 2013-09-18 19:41 Snakebite is live, and python committers can get shell access on the bots, as originally planned.

Universal Build Broken Using Python 2.7.2 Dmg For Mac Download

Some of the bots are offline, but most are running. I don't see any OS X servers in the list, though, unless Antoine deleted them (but there are several other currently-offline ones he hasn't deleted, so I doubt that).

David Murray (r.david.murray). Date: 2013-09-20 22:29 I've spun up a 10.6.8 OS X buildbot. Author: Roundup Robot (python-dev) Date: 2013-10-19 04:36 New changeset by Ned Deily in branch 'default': Issue: Change the OS X installer build script to use CFLAGS instead - Author: Andrew Barnert (abarnert). Date: 2013-10-25 00:05 Now that Xcode 5 is out, and does not have anything named 'gcc-4.2' (it does still have something called 'gcc', which is now a wrapper around clang instead of a wrapper around llvm-gcc-4.2), this seems a lot more critical, because (as far as I can tell) nobody with Xcode 5 can build C extensions for python.org Python installations.

And that also implies that any changes need to be backported to 2.7 and 3.3, unless the plan is that only Python 3.4+ should work with Xcode 5. Author: Ned Deily (ned.deily). Date: 2013-10-25 01:37 'nobody with Xcode 5 can build C extensions for python.org Python installations' Andrew, can you elaborate on what problems you or others are seeing? Xcode 5 should not be an issue for users of the current python.org Pythons. When building extension modules, if the compiler Python was built with is not available Distutils in the current 2.7.x, 3.3.x, and 3.4.x release will substitute clang.

Universal Build Broken Using Python 2.7.2 Dmg For Mac Pro

This assumes they have the Command Line Tools installed, either through Xcode or the standalone CLT package and assumes that the user is not overriding defaults by setting environment variables like CC and LDSHARED which Distutils will honor without attempting to modify them. This should all be independent of what compiler Python was built with. Author: Roundup Robot (python-dev) Date: 2013-10-25 07:54 New changeset by Ned Deily in branch '2.7': Issue: Change the OS X installer build script to use CFLAGS instead New changeset by Ned Deily in branch '3.3': Issue: Change the OS X installer build script to use CFLAGS instead - Author: Ned Deily (ned.deily). Date: 2018-04-14 14:37 New changeset by Ned Deily in branch '2.7': 2.7 Backport macOS universal build and installer fixes from 3.6. - Author: Ned Deily (ned.deily). Date: 2018-04-14 14:56 New changeset by Ned Deily in branch '2.7': 2.7 Fix errant NEWS item: - - Author: Ned Deily (ned.deily). Date: 2018-04-15 20:41 As of 3.6.5, 2.7.15, and the upcoming 3.7.0.

Universal Build Broken Using Python 2.7.2 Dmg For Mac

The macOS installers now build with a generic 'gcc' specified, rather than the somewhat confusing 'gcc-4.2' and we also provide a new 10.9+ 64-bit-only installer variant that is built with clang. So I think we can finally close this issue.