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

[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

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

[ANN] PyObjC 5.0b1
by Ronald Oussoren Sept. 2, 2018

Sept. 2, 2018

Hi, I just uploaded PyObjC 5.0b1 to PyPI. This is the first beta of the version of PyObjC that includes support for macOS 10.14 (Mojave). I expect to release 5.0 soon after the GM release of Xcode 10. The primary new “feature” as compared with the 5.0a1 is that this release includes binary wheels for all supported versions of Python (2.7, 3.4, 3.5, 3.6 and 3.7, and for 2.7, 3.6 and 3.7 there are wheels for both the older “intel” installer and the newer 64-bit installer on Python.org) Changes w.r.t. PyObjC 5.0a1: * Bindings updated for Xcode 10 beta 6. * Add a custom binding for a number of structure types in CoreAudio: - AudioBuffer - AudioBufferList - AudioChannelDescription - AudioChannelLayout - AudioValueTranslation With this patch using APIs with these types should actually work. * 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. .. note:: The creation of these objects is a sign that APIs are not wrapped correctly, these objects are created for pointers where the bridge doesn't know how to handle them properly. * 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. * #244: Bad metadata for CGPDFOperatorTableSetCallback * #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. Regards, Ronald

1 0