PyObjC SharedWithYou 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 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. While explicit memory management is rarely needed in Python, understanding the underlying Objective-C semantics is crucial for correct behavior.
• breaking In PyObjC 10.3, the ability to call `__init__` when a class or its superclasses contain a user implementation of `__new__` was temporarily dropped, then reintroduced in 10.3.1 due to breaking popular projects. Code relying on PyObjC's provided `__new__` still cannot use `__init__` in this scenario.
  Fix: If experiencing issues with `__init__` and `__new__` in custom subclasses, ensure you are on PyObjC 10.3.1 or later. If relying on PyObjC's `__new__`, avoid implementing `__init__` in that specific context.
• breaking The `IMServicePlugIn` framework bindings were removed in PyObjC 10.0 because the framework was deprecated in macOS 10.13 and removed entirely in macOS 14.
  Fix: Applications relying on `IMServicePlugIn` functionality will need to refactor to use alternative macOS APIs or ensure compatibility with older macOS versions and PyObjC releases.
• gotcha PyObjC 11.0 introduced experimental support for free-threading (PEP 703) in Python 3.13. While a significant advancement, it's an experimental feature and may have stability considerations.
  Fix: Exercise caution when using PyObjC with Python 3.13's experimental free-threading. Thorough testing is recommended for multi-threaded applications. The PyObjC team continues to refine this support.
• gotcha As of PyObjC 12.0, classes `NSString` and `NSMutableString` are marked as 'final', meaning they can no longer be subclassed from Python. Attempting to subclass them will result in crashes due to special handling within PyObjC.
  Fix: Avoid subclassing `NSString` or `NSMutableString` in Python. If custom string-like behavior is needed, wrap `NSString` instances or use standard Python string types instead.

Install

• pip install pyobjc-framework-sharedwithyou Install latest version

Imports

• SharedWithYou

  import SharedWithYou

  Imports the entire SharedWithYou framework for access to its classes and functions.

Quickstart

This quickstart demonstrates the fundamental interaction pattern with Objective-C frameworks using PyObjC, specifically showing how to import and interact with a basic Foundation object. Classes within the SharedWithYou framework would be imported and instantiated similarly through the `SharedWithYou` module.

import Foundation
import SharedWithYou # Assuming SharedWithYou classes are directly exposed

# This example demonstrates basic PyObjC interaction by creating a Foundation object.
# Interactions with SharedWithYou classes would follow a similar pattern.

# Create an instance of a Foundation object
hello_string = Foundation.NSString.stringWith_('Hello from PyObjC SharedWithYou!')
print(f"Created Objective-C string: {hello_string}")

# You would typically interact with SharedWithYou classes here.
# For example, if there was a 'SWYCollaboration' class:
# try:
#     collaboration = SharedWithYou.SWYCollaboration.alloc().init()
#     print(f"Created SharedWithYou Collaboration object: {collaboration}")
# except AttributeError:
#     print("SWYCollaboration class not found or initialized in this simple example.")

print("PyObjC bridge is active and ready to interact with macOS frameworks.")