Bump pyobjc-framework-colorsync from 9.2 to 11.0 in /tools

[dependabot]

Bumps pyobjc-framework-colorsync from 9.2 to 11.0.

Release notes

Sourced from pyobjc-framework-colorsync's releases.

v10.3.2

• Fix a number of test failures on macOS 15 These are all documentation and test updates.

• #593: PyObjCTools.AppHelper.runConsoleEventLoop no longer exits the process on macOS 14 or later when stopping the event loop.

• #613: Actually expose protocols KHTTPCookieStoreObserver, WKURLSchemeTask, and WKURLSchemeHandler in the WebKit bindings.

• Remove workaround for a linker problem in early versions of Xcode 15, which restores support for building with Xcode Command Line tools.

• The release contains wheels for the free-threaded build of Python 3.13.

  Note that PyObjC does not support running without the GIL at this time.

• Fix for running test suite with recent versions of setuptools

  Recent versions of setuptools broke the "test" command, the full command has been reimplemented as part of PyObjC.

• #627: Fix build issue when deployment target is 15.0 or later.

• #623: Don't lowercase the first character of the first keyword argument for __new__ when the segment only contains upper case characters.

  Before this change initWithURL: mapped to an uRL keyword argument, with this fix the keyword argument is named URL.

  Fix by user @​rndblnch on github

• #625: Fix crash for calling NSIndexSet.alloc().initWithIndex_(0)

  This "fix" is a workaround for what appears to be a bug in Foundation.

• #569: Actually remove the workaround for Xcode 15.0

• #619: Fix race condition in creating proxy objects for Objective-C classes.

v10.3.1

• #610: Ensure __init__ can be used when user implements __new__.

  Version 10.3 dropped support for calling __init__, but that breaks a number of popular projects. Reintroduce the ability to use __init__ when a class or one of its super classes contains a user implemenentation of __new__.

  Code relying on the __new__ provided by PyObjC still cannot use __init__ for the reason explained in the 10.3 release notes.

v10.3

• The release contains binary wheels for Python 3.13

  PyObjC does at this time not support the experimental free threading support in Python 3.13.

... (truncated)

Changelog

Sourced from pyobjc-framework-colorsync's changelog.

Version 11.0

The major change in this release is experimental support for free-threading (PEP 703 <https://peps.python.org/pep-0703/>_) which was introduced as an experimental feature in Python 3.13.

This required fairly significant changes in the core of PyObjC to change C Python API use and PyObjC internal APIs (mostly related to the use of borrowed references).

• Dropped support for Python 3.8. PyObjC 11 supports Python 3.9 and later.

• Updated metadata for the macOS 15.2 SDK, including bindings for the following frameworks:

  • MediaExtension
  • DeviceDiscoveryExtension

• :issue:249: Added minimal bindings to the Carbon framework.

  At this time only some functions and constants related to hotkeys are available. Please file an issue if you have a usecase for other APIs.

• :issue:615: Struct wrappers now support a number of functions from :mod:copy: :func:copy.replace (new in Python 3.13), :func:copy.copy and :func:copy.deepcopy.

• The __pyobjc_copy__ method has been removed from struct wrappers. This was never a public API. Use :func:copy.deepcopy instead.

• :meth:`objc.FSRef.from_pathnow supportsos.PathLike`` values as its arguments (as well as strings).

• :issue:608: Experimental support for the free-threading mode introduced in Python 3.13.

  The core bridge and framework bindings claim compatibility with free-threading as introduced as an experimental feature in Python 3.13.

  The support in PyObjC is also an experimental feature: I've reviewed code for free-threading issues and adjusted it where needed, but the code has seen only light testing w.r.t. concurrency.

  Some functionality that's explicitly not thread-safe:

  • Defining an Objective-C class with the same name in multiple threads concurrently.

  • Splitting calls to alloc and init and calling init multiple times concurrently. E.g.:

... (truncated)

Commits

• e29d3a0 Fix free-threaded support in wheel builder
• 4ee97ee Fix incorrect reference count update
• d5a101c Merge branch 'master' of github.com:ronaldoussoren/pyobjc
• 0d6caeb Minor coverage tweaks
• a80220e Slightly better test coverage
• 4ded409 Simply the generic new construction code
• a513505 More work on test coverage
• 36c2229 Reenable -O3
• 650587a Fix some static analyzer warnings in tests
• 3498633 Merge branch 'master' of github.com:ronaldoussoren/pyobjc
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)