PyObjC ExtensionKit Framework

Warnings

• breaking PyObjC frequently drops support for older Python versions. PyObjC 12.0 dropped support for Python 3.9, and PyObjC 11.0 dropped Python 3.8. Ensure your Python version is compatible with the PyObjC version you are installing.
  Fix: Upgrade your Python environment to Python 3.10 or later for PyObjC 12.x. Always check `requires_python` on PyPI or the PyObjC changelog for specific version requirements.
• breaking PyObjC 11.1 changed how initializer methods (`init` family) are modeled, now correctly reflecting that they 'steal' a reference to `self` and return a new one, as per clang's Automatic Reference Counting (ARC) documentation. This affects object lifecycle and reference counting.
  Fix: Review code that interacts with object initialization, especially custom subclasses or factory methods, to ensure correct reference handling. Explicit memory management is rarely needed in Python, but understanding the underlying Objective-C semantics is crucial for correct behavior.
• gotcha Version 10.3 introduced a change affecting the use of `__init__` when a class or its superclasses implement a custom `__new__` method, causing it to break. This was partially reverted in version 10.3.1 to reintroduce the ability to use `__init__` in such cases.
  Fix: If experiencing issues with `__init__` and custom `__new__` implementations after upgrading to 10.3, ensure you are using 10.3.1 or later. Avoid relying on `__init__` if using PyObjC's provided `__new__` method, as detailed in the 10.3 release notes.
• breaking `objc.classAddMethods` no longer supports arbitrary callable objects for adding methods to Objective-C classes.
  Fix: For `objc.classAddMethods`, ensure the added methods are appropriate for Objective-C method dispatch. Review and adapt code that uses `objc.classAddMethods` with complex callable types.
• breaking Entire framework bindings may be removed if Apple deprecates and removes the underlying macOS framework. For example, the `IMServicePlugIn` bindings were removed in PyObjC 10.0 because the framework was deprecated in macOS 10.13 and removed in macOS 14.
  Fix: Stay informed about macOS framework deprecations. If migrating to a new macOS version, consult the PyObjC changelog for any removed framework bindings and update your application to use alternative APIs or frameworks.

Install

• pip install pyobjc-framework-extensionkit Install pyobjc-framework-extensionkit

Imports

• ExtensionKit

  import ExtensionKit

  PyObjC framework wrappers are typically imported as top-level modules named after the framework.

Quickstart

This quickstart verifies the successful installation and import of the `ExtensionKit` Python bindings. Practical use of `ExtensionKit` typically involves building a macOS application extension using Xcode and interacting with it programmatically, making a standalone Python-only example challenging without an external host application context.

import ExtensionKit
import objc

print(f"Successfully imported ExtensionKit wrapper from PyObjC.")

# In a real macOS application development scenario, ExtensionKit types
# (like EXExtension, EXExtensionContext) would be used within the context
# of defining or interacting with an application extension (e.g., share extension,
# custom UI extension). 
#
# A direct Python-only example demonstrating meaningful ExtensionKit
# functionality without an accompanying Xcode project and host application
# is not straightforward. This quickstart primarily verifies the installation
# and import of the Python bindings for the framework.
#
# To see available symbols, you could inspect the module:
# print(dir(ExtensionKit))