Changelog
### 9.0a1
```
-------------
* Support for macOS 13 (Xcode 14 beta 4)
* Updated framework bindings for macOS 13
The list below lists the frameworks that have
API changes that affect the framework bindings.
* Added bindings for the following frameworks
(all new in macOS 13):
- AVRouting
- BackgroundAssets
- ExtensionKit
- HealthKit
- MetalFX
- SharedWithYou
- SharedWithYouCore
* The definition of a number of basic structs has moved in the SDK for
macOS 13 and PyObjC conforms to this change on all platforms.
In particular:
- ``CGPoint``, ``CGSize``, ``CGVector``, ``CGRect``, ``CGAffineTransform`` and ``CGAffineTransformComponents``
are now defined in the ``CoreFoundation`` module.
- ``NSPoint``, ``NSSize`` and ``NSRect`` are now aliases for the corresponding ``CG*`` types
(instead of the other way around in previous versions of PyObjC).
Both changes should require no changes to scripts, unless code relies on the
particular ``__name__`` of a type.
* 416: PyObjC 9.0 requires Python 3.7 or later
* 384: Remove support for BridgeSupport files
The bridge itself hasn't used these files for a long time, and system
bridgesupport files are basically unusable.
* 415: Remove ``objc._setClassExtender``
This was an internal function that's no longer used by PyObjC itself.
* 429: Remove ``-[OC_PythonNumber getValue:forType:]``
This method is never actually used by the system and is not
part of the ``NSNumber`` interface (but possibly was in the past)
* 438: Removed bindings for the ``Message`` and ``ServerNotification``
frameworks.
Both frameworks were removed in macOS 10.9 and hence cannot be
used on a platform that's still supported by PyObjC.
* 451: Removed the ``type`` attribute for ``ObjCPointer``
The ``typestr`` attribute contains the same value and has
more consistent naming with the rest of PyObjC.
* 436: ``Quarrtz.CVPixelBufferCreateWithBytes`` now conforms to the
PyObjC standard for returning values: it returns a tuple of two
values, the C return value and the value return through ``pixelBufferOut``.
In older versions the return value was only the value return through
``pixelBufferOut``.
* 464: The encodings ``objc._C_NSBOOL`` and ``objc._C_BOOL`` are now treated
exactly the same as the types ``BOOL`` and ``bool`` have the same size
and representation on arm64 and x86_64.
* 94: Add support for SIMD types in APIs (types such as ``vector_float3``)
The python representation of these types are types with the same name in
defined in :mod:`objc.simd`.
Because the FFI library used by PyObjC (libffi) does not support these types
the bridge only supports the method signatures found in system frameworks,
other signatures will result in exceptions at runtime.
* Because of the previous change APIs that have a SIMD type are now callable
from Python.
* Changes due to generic implementation for SIMD types:
- ``SpriteKit.SK3DNode.projectPoint_``: The result is now ``objc.simd.vector_float3`` instead of a tuple
- ``SpriteKit.SK3DNode.unprojectPoint_``: The result is now ``objc.simd.vector_float3`` instead of a tuple
- ``SpriteKit.SKFieldNode.direction``: The result is now ``objc.simd.vector_float3`` instead of a tuple
- ``SpriteKit.SKPhysicsWorld.sampleFieldsAt_``: The result is now ``objc.simd.vector_float3`` instead of a tuple
* Still not supported (requires some more infrastructure):
- ``SpriteKit.SKFieldNode.customFieldWithEvaluationBlock_``
* The registered metadata can now contain a key ``full_signature`` with the
full encoding type signature for a method. This is used to replace the
encoding extracted from the Objective-C runtime when one or more types have
an empty encoding in the Objective-C runtime (such as the SIMD types mentioned
earlier)
```
### 8.6
```
-----------
* 468: Fix setup.py for framework bindings to ensure that
``python setup.py build_ext`` works for bindings that don't
contain a C extension.
* Fix incompatibilities with Python 3.11 (beta 1)
- Switch to ``PyCode_GetCode`` instead of accessing
the ``co_code`` field on Python 3.11.
- Add definition for ``PassKit.PKPaymentNetworkAppleStoredValue``
(actually using this won't work as the constant is not
present on macOS 12.4 even though the SDK seems to suggest
otherwise)
* Add definition for ``objc.MAC_OS_X_VERSION_12_4``
```
Links
- PyPI: https://pypi.org/project/pyobjc
- Changelog: https://pyup.io/changelogs/pyobjc/
- Repo: https://github.com/ronaldoussoren/pyobjc
pyup-bot
commented
1 year ago
This PR updates pyobjc from 8.5.1 to 9.0.
Changelog
### 9.0a1 ``` ------------- * Support for macOS 13 (Xcode 14 beta 4) * Updated framework bindings for macOS 13 The list below lists the frameworks that have API changes that affect the framework bindings. * Added bindings for the following frameworks (all new in macOS 13): - AVRouting - BackgroundAssets - ExtensionKit - HealthKit - MetalFX - SharedWithYou - SharedWithYouCore * The definition of a number of basic structs has moved in the SDK for macOS 13 and PyObjC conforms to this change on all platforms. In particular: - ``CGPoint``, ``CGSize``, ``CGVector``, ``CGRect``, ``CGAffineTransform`` and ``CGAffineTransformComponents`` are now defined in the ``CoreFoundation`` module. - ``NSPoint``, ``NSSize`` and ``NSRect`` are now aliases for the corresponding ``CG*`` types (instead of the other way around in previous versions of PyObjC). Both changes should require no changes to scripts, unless code relies on the particular ``__name__`` of a type. * 416: PyObjC 9.0 requires Python 3.7 or later * 384: Remove support for BridgeSupport files The bridge itself hasn't used these files for a long time, and system bridgesupport files are basically unusable. * 415: Remove ``objc._setClassExtender`` This was an internal function that's no longer used by PyObjC itself. * 429: Remove ``-[OC_PythonNumber getValue:forType:]`` This method is never actually used by the system and is not part of the ``NSNumber`` interface (but possibly was in the past) * 438: Removed bindings for the ``Message`` and ``ServerNotification`` frameworks. Both frameworks were removed in macOS 10.9 and hence cannot be used on a platform that's still supported by PyObjC. * 451: Removed the ``type`` attribute for ``ObjCPointer`` The ``typestr`` attribute contains the same value and has more consistent naming with the rest of PyObjC. * 436: ``Quarrtz.CVPixelBufferCreateWithBytes`` now conforms to the PyObjC standard for returning values: it returns a tuple of two values, the C return value and the value return through ``pixelBufferOut``. In older versions the return value was only the value return through ``pixelBufferOut``. * 464: The encodings ``objc._C_NSBOOL`` and ``objc._C_BOOL`` are now treated exactly the same as the types ``BOOL`` and ``bool`` have the same size and representation on arm64 and x86_64. * 94: Add support for SIMD types in APIs (types such as ``vector_float3``) The python representation of these types are types with the same name in defined in :mod:`objc.simd`. Because the FFI library used by PyObjC (libffi) does not support these types the bridge only supports the method signatures found in system frameworks, other signatures will result in exceptions at runtime. * Because of the previous change APIs that have a SIMD type are now callable from Python. * Changes due to generic implementation for SIMD types: - ``SpriteKit.SK3DNode.projectPoint_``: The result is now ``objc.simd.vector_float3`` instead of a tuple - ``SpriteKit.SK3DNode.unprojectPoint_``: The result is now ``objc.simd.vector_float3`` instead of a tuple - ``SpriteKit.SKFieldNode.direction``: The result is now ``objc.simd.vector_float3`` instead of a tuple - ``SpriteKit.SKPhysicsWorld.sampleFieldsAt_``: The result is now ``objc.simd.vector_float3`` instead of a tuple * Still not supported (requires some more infrastructure): - ``SpriteKit.SKFieldNode.customFieldWithEvaluationBlock_`` * The registered metadata can now contain a key ``full_signature`` with the full encoding type signature for a method. This is used to replace the encoding extracted from the Objective-C runtime when one or more types have an empty encoding in the Objective-C runtime (such as the SIMD types mentioned earlier) ``` ### 8.6 ``` ----------- * 468: Fix setup.py for framework bindings to ensure that ``python setup.py build_ext`` works for bindings that don't contain a C extension. * Fix incompatibilities with Python 3.11 (beta 1) - Switch to ``PyCode_GetCode`` instead of accessing the ``co_code`` field on Python 3.11. - Add definition for ``PassKit.PKPaymentNetworkAppleStoredValue`` (actually using this won't work as the constant is not present on macOS 12.4 even though the SDK seems to suggest otherwise) * Add definition for ``objc.MAC_OS_X_VERSION_12_4`` ```Links
- PyPI: https://pypi.org/project/pyobjc - Changelog: https://pyup.io/changelogs/pyobjc/ - Repo: https://github.com/ronaldoussoren/pyobjc