1899440 - [wpt-sync] Sync PR 46523 - Bump pyobjc-framework-quartz from 9.2 to 10.3 in /tools

Status: RESOLVED INVALID

(Testing :: web-platform-tests, task, P4)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Sync web-platform-tests PR 46523 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/46523
Details from upstream follow.

dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> wrote:

Bump pyobjc-framework-quartz from 9.2 to 10.3 in /tools

Bumps pyobjc-framework-quartz from 9.2 to 10.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/ronaldoussoren/pyobjc/releases">pyobjc-framework-quartz's releases</a>.</em></p>
<blockquote>
<h2>v10.3</h2>
<ul>
<li>
<p>The release contains binary wheels for Python 3.13</p>
<p>PyObjC does at this time not support the experimental free threading
support in Python 3.13.</p>
</li>
<li>
<p><a href="https://redirect.github.com/ronaldoussoren/pyobjc/issues/569">#569</a>: Removed the workaround for a bug in Xcode 15.0</p>
<p>The workaround is no longer necessary, and caused problems when
building with the Command Line Tools development tools from Apple.</p>
</li>
<li>
<p>Updated SDK bindings for macOS 14.5</p>
</li>
<li>
<p>A minor change in the (currently private) tooling I use for
collecting the raw metadata resulted in minor fixes to the framework
bindings, in particular for metadata for a number of block and function
typed arguments and return values.</p>
</li>
<li>
<p><a href="https://redirect.github.com/ronaldoussoren/pyobjc/issues/275">#275</a>: It is now possible to create instances of Objective-C
classes by calling the class, e.g. <code>NSObject()</code> instead of
<code>NSObject.alloc().init()</code>.</p>
<p>The implementation of <code>__new__</code> forwards calls to the underlying
<code>SomeClass.alloc().init...()</code> pattern. In particular, all public init
methods are translated into sets of keyword arguments:</p>
<ul>
<li>Remove <code>init</code> or <code>initWith</code> from the start of the selector name</li>
<li>Lowercase the first character of what's left over</li>
<li>The strings before colons are acceptable keywords, in that order</li>
</ul>
<p>For example, given a selector <code>initWithX:y:</code> the <code>__new__</code> method
will accept <code>x, y</code> as keyword arguments, in that order.</p>
<p>Framework bindings have been updated with additional metadata to support
this pattern, and the sets of keyword arguments are automatically calculated
for subclasses in written in Python.</p>
<p>The limitation on the order of keyword arguments may be lifted in a future
version, it is currently present to keep the code closer to the Objective-C
spelling which should make it easier to look up documentation on Apple's
website.</p>
</li>
<li>
<p>For some Objective-C classes some of the <code>init</code> and <code>new</code> methods are not
available even if they are available in super classes. Those methods are
marked with <code>NS_UNAVAILABLE</code> in Apple's headers.</p>
<p>As of this version these methods are also not available in Python code,
trying to call them will result in an exception.</p>
<p>To make methods unavailable in Python classes set these methods to <code>None</code>,</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/ronaldoussoren/pyobjc/blob/master/docs/changelog.rst">pyobjc-framework-quartz's changelog</a>.</em></p>
<blockquote>
<h2>Version 10.3</h2>
<ul>
<li>
<p>The release contains binary wheels for Python 3.13</p>
<p>PyObjC does at this time not support the experimental free threading
support in Python 3.13.</p>
</li>
<li>
<p>:issue:<code>569</code>: Removed the workaround for a bug in Xcode 15.0</p>
<p>The workaround is no longer necessary, and caused problems when
building with the Command Line Tools development tools from Apple.</p>
</li>
<li>
<p>Updated SDK bindings for macOS 14.5</p>
</li>
<li>
<p>A minor change in the (currently private) tooling I use for
collecting the raw metadata resulted in minor fixes to the framework
bindings, in particular for metadata for a number of block and function
typed arguments and return values.</p>
</li>
<li>
<p>:issue:<code>275</code>: It is now possible to create instances of Objective-C
classes by calling the class, e.g. <code>NSObject()</code> instead of
<code>NSObject.alloc().init()</code>.</p>
<p>The implementation of <code>__new__</code> forwards calls to the underlying
<code>SomeClass.alloc().init...()</code> pattern. In particular, all public init
methods are translated into sets of keyword arguments:</p>
<ul>
<li>Remove <code>init</code> or <code>initWith</code> from the start of the selector name</li>
<li>Lowercase the first character of what's left over</li>
<li>The strings before colons are acceptable keywords, in that order</li>
</ul>
<p>For example, given a selector <code>initWithX:y:</code> the <code>__new__</code> method
will accept <code>x, y</code> as keyword arguments, in that order.</p>
<p>Framework bindings have been updated with additional metadata to support
this pattern, and the sets of keyword arguments are automatically calculated
for subclasses in written in Python.</p>
<p>The limitation on the order of keyword arguments may be lifted in a future
version, it is currently present to keep the code closer to the Objective-C
spelling which should make it easier to look up documentation on Apple's
website.</p>
</li>
<li>
<p>For some Objective-C classes some of the <code>init</code> and <code>new</code> methods are not
available even if they are available in super classes. Those methods are
marked with <code>NS_UNAVAILABLE</code> in Apple's headers.</p>
<p>As of this version these methods are also not available in Python code,
trying to call them will result in an exception.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/1b015b704c982d76c7ff15ab0b81baa4fc39fec2"><code>1b015b7</code></a> Release day</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/0c2becb3fda52fa76818218b122c7784484b061e"><code>0c2becb</code></a> Fix typo</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/fe2cb68171fec5cff7297377bb60cc11bb02c70d"><code>fe2cb68</code></a> Fix off by one error in initializing objc.super</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/3574271b45ca89e1b3532bf22d31f105e7c3f88e"><code>3574271</code></a> Metadata update run with latest tooling</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/6a799d2dcdb0175ec430b8124c138b427ddb3b9d"><code>6a799d2</code></a> Revert workaround for <a href="https://redirect.github.com/ronaldoussoren/pyobjc/issues/569">#569</a></li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/7a6c6336fb232a954990dd1a678108123766da67"><code>7a6c633</code></a> Be explicit about the type of two arguments</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/fb337e1aec2647101159f6af4ae747fbc4a3c7cd"><code>fb337e1</code></a> Fix a number of metadata issues with the newly generated metadata</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/b48fd5c36bdb02cb8336ac8575314b405f1b8db8"><code>b48fd5c</code></a> Fix duplicate NSObject definition</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/2a817f801fdc963fc437edcdf3f3287f8604886b"><code>2a817f8</code></a> Adjust tests for protocol methods that are no longer relevant</li>
<li><a href="https://github.com/ronaldoussoren/pyobjc/commit/5aa3ccd6af11d7c65ea5b3bf8866f69149f72b27"><code>5aa3ccd</code></a> Add some manual definitions for constants that are not present in recent SDKs</li>
<li>Additional commits viewable in <a href="https://github.com/ronaldoussoren/pyobjc/compare/v9.2...v10.3">compare view</a></li>
</ul>
</details>
<br />

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.

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)

</details>