🌐 Mailman 3 October 2018 - Pythonmac-SIG - python.org

[ANN] PyObjC 5.1.1
by Ronald Oussoren Oct. 31, 2018

Oct. 31, 2018

Hi, I’ve pushed PyObjC 5.1.1 to PyPI. This is a very minor feature update: it adds a small number of symbols introduced in the macOS 10.14.1 SDK included with Xcode 10.1. Ronald

1 0

ctypes MemoryError when attempting to launch notarized app
by Glyph Oct. 30, 2018

Oct. 30, 2018

I adjusted my code-signing to use the new, stricter requirements imposed by app notarization. I managed to get it successfully notarized, but the app is now non-functional as a result: at startup, I get: Traceback (most recent call last): File "my.app/Contents/Resources/__boot__.py", line 93, in <module> _setup_ctypes() File "my.app/Contents/Resources/__boot__.py", line 86, in _setup_ctypes from ctypes.macholib import dyld File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 656, in _load_unlocked File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible File "ctypes/__init__.pyc", line 538, in <module> File "ctypes/__init__.pyc", line 273, in _reset_cache (If anyone wants to follow along in the traceback, this is using python.org <http://python.org/> 3.6.6.) This happens before any of my code even runs, so I can't just try to avoid ctypes. Curiously, this is the same traceback that comes from https://forum.kodi.tv/showthread.php?tid=329171 <https://forum.kodi.tv/showthread.php?tid=329171>, which suggests it's something fundamental to strict shared-library sandboxing that ctypes trips over when trying to initialize itself. Does anyone have experience with this, or ideas about what to do? -glyph

2 11

[ANN] PyObjC 5.0
by Ronald Oussoren Oct. 29, 2018

Oct. 29, 2018

PyObjC 5.0 is out The release of macOS 10.14 is near, it is therefore time to release a new major version of PyObjC. I’ve uploaded PyObjC to PyPI, it can be installed using “python3 -m pip install -U pyobjc”. What is PyObjC The PyObjC project provides bindings to most of Apple’s higher-level APIs (frameworks). More information about these bindings and how to use PyObjC can be found on the PyObjC website. What is new The main feature of this release is the addition of support for APIs introduced in macOS 10.14 (Mojave). In particular: * Adds support for macOS 10.14 (Mojave) * This release updates the framework wrappers with support for new APIs in macOS 10.14 and adds bindings for the following new frameworks: • AdSupport • CoreAudio (new in macOS 10.0) • CoreAudioKit (new in macOS 10.4) • CoreMedia (new in macOS 10.7) • CoreMediaIO (new in macOS 10.7) • DiscRecording (new in macOS 10.2) • DiscRecordingUI (new in macOS 10.2) • DVDPlayback (new in macOS 10.3) • MediaToolbox • NaturalLanguage • Network • OSAKit (new in macOS 10.4) • UserNotifications • VideoSubscriberAccount • VideoToolbox (new in macOS 10.8) * Added two features that can help with gating code on the version of macos: 1) The constants “objc.MAC_OS_X_VERSION_CURRENT” can be compared with one of the “objc.MAC_OS_X_VERSION_…” contants. 2) The function “objc.macos_avaiable(major, minor[, patch])” returns true if the current macOS version is at least the specified version, comparable with “@available” in Swift. * PR19: Fix deprecation warning in bridgesupport support module Patch by: Mickaël Schoentgen * Creating objc.ObjCPointer instances now results in a Python warning, instead of an unconditional message on stdout. * System bridgesupport XML files (normally not used by PyObjC) can contain constant numbers with value “inf”, PyObjC now knows how to handle those. * Added bindings for the “Metadata” subframework of the “CoreServices” framework. * Added bindings for the “CarbonCore” subframework of the “CoreServices” framework. Most APIs in this subframework are not available to Python, only those APIs that are not deprecated and seem interesting are exposed. * The separate framework wrappers DictionaryServices, LaunchServices and SearchKit are deprecated, use the CoreServices bindings instead. These framework wrappers still exists, but are effectively aliases for CoreServices with this release. Because of this these bindings can expose more symbols than previously. * Fix unexpected exception when trying to call getattr on a framework wrapped with a name that isn’t a valid identifier. * Issue 244: Bad metadata for CGPDFOperatorTableSetCallback * Issue 247: Fix crash in regression test case * One specific test in pyobjc-core crashed the interpreter when run separately. Because of this I’ve disabled an optimization that uses alloca instead of PyMem_Malloc to allocate memory for now. Supporting development I do all development on PyObjC in my spare time. Please consider donating if you use PyObjC professionally. This will help me to improve PyObjC and related projects. See my website for more information. P.S. This is a cross-post from http://blog.ronaldoussoren.net/2018/09/18/pyobjc-is-out.html, and I’ve also tweeted about this from @RonaldOussoren.

2 5

[ANN] PyObjC 5.1
by Ronald Oussoren Oct. 16, 2018

Oct. 16, 2018

Hi, I’ve pushed PyObjC 5.1 to PyPI. This is a minor feature release. The most interesting change is that the Objective-C proxies for builtin Python types now support NSSecureCoding. The full list of changes: Xcode 10 “GM” contains one difference from the last beta: the constant MLComputeUnitsCPUAndGPU in the CoreML bindings. #222: Add a proxy for C’s “FILE*” type on Python 3. This is not necessary on Python 2 because the default IO stack on Python 2 already uses FILE* internally. This proxy type is very minimal and shouldn’t not be used for general I/O. Bindings are up-to-date w.r.t. Xcode 10.1 (beta) Updated the support code for framework wrappers to be able to emit deprecation warnings on the first import of a deprecated constants (functions and methods will only raise a deprecation warning when called). This is just an infrastructure change, the actual framework bindings do not yet contain the information used to emit deprecation warnings. Add metadata for deprecation warnings to the “Contacts” framework #252: Import ABCs from collections.abc instead of collections because the latter is deprecated. #180, #251: Instances of most builtin value types and sequences (int, float, str, unicode, tuple, list, set, frozenset and dict) can now be written to archives that require secureCoding. Ronald

1 0

[ANN] py2app 0.18
by Ronald Oussoren Oct. 11, 2018

Oct. 11, 2018

Hi, I’ve released py2app 0.18 on PyPI. The only change w.r.t. 0.17 is a recipe for “six.moves”, that should also work when the “six” library has been vendored by some other package. Ronald

1 0

py2app -A and virtual environments
by Just van Rossum Oct. 1, 2018

Oct. 1, 2018

Hi all, py2app seems to do the right thing from an activated virtual env when building a full app. However, for speedy development I use the py2app -A option a lot, and when running such an alias bundle it appears to use the global Python install instead of the virtual env. Is there a way around that? Just

3 5