[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

Roundup Robot added the comment: New changeset 967b06d56a69 by Stefan Krah in branch 'default': Issue #14779: Get sizeof(void *) directly rather than relying on sysconfig. http://hg.python.org/cpython/rev/967b06d56a69 -- ___ Python tracker

[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

Changes by Stefan Krah : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker ___ _

[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

Stefan Krah added the comment: Apparently the AS/400 had 128 bit pointers and IBM's "System i" still has them: http://comments.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/651 http://www-01.ibm.com/support/docview.wss?uid=swg27019425 So I'll leave the SIZEOF_VOID_P test as the

[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

Roundup Robot added the comment: New changeset 8f22e5be18c8 by Stefan Krah in branch 'default': Issue #14779: Do not use get_config_var('SIZEOF_VOID_P') on OS X 64-/32-bit http://hg.python.org/cpython/rev/8f22e5be18c8 -- nosy: +python-dev ___ Python

[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

Stefan Krah added the comment: The tests for arrays with suboffsets literally need sizeof(void *). I don't think C guarantees SIZEOF_VOID_P == SIZEOF_SIZE_T. If HAVE_SSIZE_T is defined in pyport.h, AFAICS no such check is made. Of course these concerns may be entirely theoretical. :)

[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

Antoine Pitrou added the comment: Well, no need to ever use SIZEOF_VOID_P. sys.maxsize should always tell you whether the build is 32-bit or 64-bit. -- nosy: +mark.dickinson, pitrou ___ Python tracker ___

[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

Stefan Krah added the comment: The sysconfig docs say: "configuration variables relevant for the current platform" If get_config_var('SIZEOF_VOID_P') is meaningless for universal builds, then IMO it should return None. None would then mean either "not found" or "irrelevant". -- __

[issue14779] test_buffer fails on OS X universal 64-/32-bit builds

New submission from Ned Deily : test_buffer can fail when run on an OS X 64-/32-bit universal build of Python is run in 32-bit mode. $ /usr/local/bin/python3.3 -m test test_buffer [1/1] test_buffer 1 test OK. $ /usr/local/bin/python3.3-32 -m test -v test_buffer == CPython 3.3.0a3 (v3.3.0a3:0b53