[issue16280] Inconsistency with PyLong_FromVoidPtr() and PyLong_AsVoidPtr()

2012-10-18 Thread Mark Dickinson
Mark Dickinson added the comment: Dropped the special case for 3.4. I'm leaving the code as-is for the maintenance branches, as discussed in issue16277. -- assignee: -> mark.dickinson resolution: -> fixed status: open -> closed type: resource usage -> behavior __

[issue16280] Inconsistency with PyLong_FromVoidPtr() and PyLong_AsVoidPtr()

2012-10-18 Thread Roundup Robot
Roundup Robot added the comment: New changeset 5ae4ff03b35f by Mark Dickinson in branch 'default': Issue 16280: Drop questionable special-casing of null pointer in PyLong_FromVoidPtr. http://hg.python.org/cpython/rev/5ae4ff03b35f -- nosy: +python-dev ___

[issue16280] Inconsistency with PyLong_FromVoidPtr() and PyLong_AsVoidPtr()

2012-10-18 Thread Serhiy Storchaka
New submission from Serhiy Storchaka: This issue is taken out of the discussion of issue16277. PyLong_FromVoidPtr() has special case which maps null pointer to zero integer. On platforms where (uintptr_t)(void *)0 is 0, this code has no effect and is redundant. But on hypothetic platforms whe