Hi,
Iβve released py2app 0.16 and macholib 1.11 with a couple of small changes.
The most important fix is in macholib and avoids the "New Mach-O header is too large to relocate in β¦β error when using Python wheels containing shared libraries (such as Pillow).
A full list of changes in py2app 0.16:
* #244: Copy the Tcl/Tk support libraries into the application bundle for
Python builds using a classic unix install of Tcl/Tk instead of a framework
build.
This results in working app bundles when a Python.org installation that
includes Tcl/Tk (such as Python 3.7).
* Don't copy numpy into application just because the application uses
Pillow.
* Add recipe for Pyside
Patch by Alberto Sottile
And macholib 1.11:
* Add very hacky limited support for @loader_path. This is just
enough to deal with extensions and dylibs found in Python
binary wheels.
Regards,
Ronald
[This is a cross-post from http://blog.ronaldoussoren.net]
I pushed a first alpha release for PyObjC 5.0 to PyPI, it can be installed with βpip install βpre pyobcβ.
The major change in the 5.0 release is the addition of API bindings for macOS 10.14. This release is mostly up-to-date w.r.t. developer beta 3 of that release.
Other than updating existing API bindings this release adds new framework bindings for the following 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
The bindings for CoreAudio, CoreMedia and MediaToolbox arenβt fully usable in this release, I have to write C code for a number of APIs and data structures that cannot be accessed using the generic FFI in pyobjc-core.
This alpha release only included wheels for the 64-bit installer of Python 3.7 (the default download on Python.org), the final release will include the full set of wheels.
Footnote
The release is a week later and less complete than I had hoped earlier. The reason for that is primarily that I was too optimistic on the amount of work Iβd be able to do before and during EuroPython. In the end I barely touched my computer for PyObjC work at EuroPython, and not at all during the trip around Scotland beforehand (both of which were good for me, but less so for making progress)
Regard,
Ronald