PyObjC Framework FileProviderUI

Warnings

• breaking PyObjC 12.0 dropped support for Python 3.9. PyObjC 11.0 dropped support for Python 3.8. Ensure your Python version meets the `>=3.10` requirement.
  Fix: Upgrade to Python 3.10 or newer. Check `requires_python` in `pyproject.toml` or PyPI for the specific version range.
• breaking The behavior of `__init__` for Objective-C classes subclassed in Python changed in PyObjC 10.3, leading to breakage for projects using `__init__` in conjunction with a `__new__` provided by PyObjC. This was partially reverted in 10.3.1 to allow `__init__` when a user-defined `__new__` is present, but code relying on PyObjC's default `__new__` still cannot use `__init__`.
  Fix: If subclassing Objective-C classes, consider using the `SomeClass(...)` instantiation pattern introduced in PyObjC 10.3 instead of `alloc().init...()`. If implementing a custom `__new__`, ensure it correctly handles object creation and delegates to super if necessary, or upgrade to 10.3.1+ if relying on `__init__` with a custom `__new__`.
• gotcha PyObjC 11.0 introduced experimental support for free-threading (PEP 703) with Python 3.13. While this aims to improve concurrency, it involved significant changes in the core bridge and might introduce unexpected behavior or require specific handling in multithreaded applications.
  Fix: If using Python 3.13+ with free-threading, thoroughly test concurrent Objective-C interactions. Consult PyObjC documentation for any specific guidelines on free-threading.
• gotcha When pinning dependencies for cross-platform projects, `pyobjc-core` (and by extension framework wrappers) should be explicitly restricted to macOS using `sys_platform == "darwin"` in `requirements.txt` or similar, as installation will fail on non-macOS platforms.
  Fix: Add `pyobjc-core; sys_platform == "darwin"` and other `pyobjc-framework-*` packages with the same platform specifier to your project's dependencies.
• gotcha Some Cocoa classes are marked as non-subclassable in the macOS SDK. Attempting to subclass these from Python via PyObjC can lead to crashes.
  Fix: Refer to Apple's documentation for the specific Objective-C class you intend to subclass and verify if it supports subclassing. Avoid subclassing classes marked as non-subclassable.
• deprecated The `isAlloc` attribute of `objc.selector` has been deprecated and is scheduled for removal in PyObjC 12.
  Fix: Update your code to avoid relying on the `isAlloc` attribute of `objc.selector`.

Install

• pip install pyobjc-framework-fileproviderui Install latest version

Imports

• FileProviderUI

  import FileProviderUI

Quickstart

This quickstart demonstrates how to import the `FileProviderUI` framework and access a common class, `FPUIActionExtensionContext`, to print its description. This verifies the successful loading and bridging of the framework. This script should be run on macOS.

import FileProviderUI
import Foundation # Often needed for basic Cocoa objects like NSString, NSObject

def main():
    print(f"FileProviderUI module loaded: {FileProviderUI}")
    # Try to access a known class from the framework and print its description
    # FPUIActionExtensionContext is a common class in FileProviderUI
    if hasattr(FileProviderUI, 'FPUIActionExtensionContext'):
        context_class = FileProviderUI.FPUIActionExtensionContext
        print(f"FPUIActionExtensionContext class: {context_class}")
        print(f"Description of FPUIActionExtensionContext: {context_class.description()}")
    else:
        print("FPUIActionExtensionContext not found. This might indicate an older macOS SDK or an internal API.")

if __name__ == "__main__":
    main()