[issue40198] macOS Python builds from Python.org ignore DYLD_LIBRARY_PATH due to hardened runtime

2020-04-20 Thread dgelessus
dgelessus added the comment: I can confirm that the newly released Python 2.7.18 has the .allow-dyld-environment-variables entitlement: $ ./python2.7 --version Python 2.7.18 $ codesign --display --entitlements=:- python2.7 Executable=/Library/Frameworks/Python.framework/Versions/2.7/bin

[issue40198] macOS Python builds from Python.org ignore DYLD_LIBRARY_PATH due to hardened runtime

2020-04-05 Thread dgelessus
New submission from dgelessus : Recent Python.org versions of Python for macOS no longer respect the DYLD_LIBRARY_PATH environment variable for extending the dynamic library search path, and the envvar is completely invisible to the Python process. This is the case since at least Python

[issue39948] Python 3.8 unconditionally uses functions not available on OS X 10.4 and 10.5

2020-03-14 Thread dgelessus
Change by dgelessus : -- keywords: +patch pull_requests: +18353 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19008 ___ Python tracker <https://bugs.python.org/issu

[issue39948] Python 3.8 unconditionally uses functions not available on OS X 10.4 and 10.5

2020-03-12 Thread dgelessus
New submission from dgelessus : In particular, the implementation of posix._fcopyfile uses (available since OS X 10.5), and the implementation of threading.get_native_id uses pthread_threadid_np (available since OS X 10.6). This breaks builds for OS X 10.5 and older. I'm aware tha

[issue38291] Unclear status of the typing.io and typing.re pseudo-modules in docs and runtime

2019-09-27 Thread dgelessus
New submission from dgelessus : According to bpo-35089 (and the GitHub issues linked there), the typing.io and typing.re modules should no longer be used. Starting with Python 3.6, the typing documentation no longer mentions the typing.io and typing.re modules, and instead documents their

[issue36880] Returning None from a callback with restype py_object decrements None's refcount too much

2019-05-16 Thread dgelessus
Change by dgelessus : -- keywords: +patch pull_requests: +13273 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36880> ___ ___ Python-

[issue36880] Returning None from a callback with restype py_object decrements None's refcount too much

2019-05-13 Thread dgelessus
dgelessus added the comment: Thank you for looking into this! I can confirm that Eryk Sun's change fixes the issue for me locally. I'm up for making the patch for this. Regarding tests, I see there are already some refcount-related ctypes tests in Lib/ctypes/test/test_refcounts.py

[issue36880] Returning None from a callback with restype py_object decrements None's refcount too much

2019-05-10 Thread dgelessus
New submission from dgelessus : This occurs when writing a ctypes callback in Python whose restype is ctypes.py_object. If the callback returns None, the refcount of None is decremented once too often. This happens every time the callback is called, and if done often enough, Python attempts