Ned Deily added the comment: Right. precisionbigmemtest was added by 0aafd1ae5120 ("security patches from Apple") and released in 2.5.3. OS X 10.5 ("Leopard") has 2.5.1. On a hunch, I installed a python2.4 (2.4.4) and the tests are broken using that as well: multiple failures attempting to import _2G
====================================================================== ERROR: test_simple_newobj (test.test_xpickle.CPicklePython24Compat) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/test/pickletester.py", line 877, in test_simple_newobj s = self.dumps(x, proto) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/test/test_xpickle.py", line 115, in dumps return self.send_to_worker(self.python, arg, proto) File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/test/test_xpickle.py", line 111, in send_to_worker raise RuntimeError(stderr) RuntimeError: Traceback (most recent call last): File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/test/test_xpickle.py", line 28, in ? exec compile(open(mod_path).read(), mod_path, 'exec') in pickletester.__dict__ File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/test/pickletester.py", line 9, in ? from test.test_support import (TestFailed, have_unicode, TESTFN, _2G, _1M, ImportError: cannot import name _2G ---------- stage: -> needs patch title: test_xpickle fails on OS X 10.5 with "cannot import name precisionbigmemtest" -> test_xpickle fails with "cannot import name precisionbigmemtest" or "cannot import name _2G" _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17533> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com