PyObjC DiscRecording Framework

Warnings

• breaking PyObjC versions frequently drop support for older Python versions. PyObjC 12.0 dropped Python 3.9, and PyObjC 11.0 dropped Python 3.8. Ensure your Python environment meets the `requires_python` specification for your PyObjC version.
  Fix: Upgrade your Python interpreter to a supported version (e.g., Python 3.10+ for PyObjC 12.1) before upgrading PyObjC.
• breaking Starting with PyObjC 11.1, the core bridge's Automatic Reference Counting (ARC) behavior for initializer methods (those in the 'init' family) was updated to more closely align with `clang` documentation. This means `init` methods now correctly 'steal' a reference to `self` and return a new one. Code that manually manages reference counts around `init` calls might need adjustment.
  Fix: Review code that interacts with `init` family methods, especially if it relies on manual `retain`/`release` or assumes specific reference counts before and after `init` calls. Trust PyObjC's ARC modeling unless you have specific reasons otherwise.
• gotcha In PyObjC 10.3, there was a change affecting how `__init__` is called when a class implements its own `__new__`. While partially reverted in 10.3.1, code relying on the PyObjC-provided `__new__` (i.e., not overridden in Python) still cannot use `__init__`. If you implement `__new__` in your Python subclass of an Objective-C class, `__init__` will be called. Otherwise, it won't.
  Fix: If you override `__new__` in a Python subclass, ensure `__init__` is correctly implemented. If you rely on PyObjC's default `__new__`, be aware that `__init__` will not be called, and perform initialization directly in `__new__` or another appropriate method.
• gotcha PyObjC does not currently support Python's experimental free-threading (PEP 703), which was introduced in Python 3.13. Running PyObjC with a free-threading enabled Python 3.13 interpreter may lead to unexpected behavior or crashes.
  Fix: If using Python 3.13, ensure it is not compiled with free-threading support enabled, or use a Python version for which free-threading is not a factor when working with PyObjC.
• gotcha As of PyObjC 10.1, `os.fspath()` will not work directly with Cocoa `NSURL` or `CFURLRef` objects that do not refer to local filesystem paths, raising a `TypeError`. It only works for URLs convertible to local paths.
  Fix: For non-filesystem-bound URLs, use Cocoa methods to extract string representations (e.g., `url.absoluteString()`) rather than relying on `os.fspath()` for path-like object conversion.

Install

• pip install pyobjc-framework-discrecording Install pyobjc-framework-discrecording

Imports

• DiscRecording

  import DiscRecording

  The framework itself is imported as a module.
• DRDevice

  from DiscRecording import DRDevice

  Classes within the framework are directly exposed in the top-level framework module, not the PyPI package name.

Quickstart

This example demonstrates how to import the DiscRecording framework and list all detected disc burning devices on the system, printing their basic information. This uses the `DRDevice` class to query device properties.

import DiscRecording
import objc

def list_disc_devices():
    devices = DiscRecording.DRDevice.allDevices()
    if not devices:
        print("No disc burning devices found.")
        return

    print("Available Disc Devices:")
    for device in devices:
        print(f"  Name: {device.displayName()}")
        print(f"  Vendor: {device.vendorName()}")
        print(f"  Product: {device.productName()}")
        print(f"  Bus: {device.busName()}")
        print(f"  Write Capabilities: {device.writeCapabilities()['DRDeviceCanWriteDisc']}")
        print(f"  Can Burn: {device.canBurn()}")
        print("  ---")

if __name__ == "__main__":
    # Ensure the Objective-C runtime is initialized
    # (often handled automatically in app contexts, but explicit for scripts)
    list_disc_devices()