Bump pyobjc-framework-quartz from 11.0 to 11.1 in /tools
Bumps pyobjc-framework-quartz from 11.0 to 11.1.
Release notes
Sourced from pyobjc-framework-quartz's releases.
v11.1
The major change in this release is aligning behaviour of the core bridge with
clang's documentation for automatic reference counting <https://clang.llvm.org/docs/AutomaticReferenceCounting.html>_ for initializer methods. In particular, PyObjC now correctly models that methods in the "init" family steal a reference to self and return a new reference.In previous version of PyObjC the proxy for
[NSObject alloc]would be marked as 'partially initialized' and would be cleared when the-initmethod returns something else thenself.This has two problems:
Behaviour is incorrect when
+allocreturns a singleton whose-initmethod(s) are factory methods (such asNSArrayin recent versions of macOS)The proxy for Objective-C objects needs to contain mutable state. This in turn requires locking in the implementation to work correctly with free-threading.
This version drops the concept of "uninitialized" values and correctly models how reference counts are handled by
-initmethods.
Update framework bindings for the macOS 15.5 SDK
Added bindings for the
SecurityUIframeworkRestructure the PyObjC website
The theme of the PyObjC websites is now shibuya to give a more modern look and feel to the website.
The actual content is mostly still the same, with some minor restructuring of pages. Restructuring will continue in future updates.
:class:
objc.FSRefnow implements :class:os.PathLike.:issue:
642: Fix concurrency issue when creatingNSArrayinstances usingNSArray.alloc().init....In previous versions the following would fail on recent versions of macOS:
.. sourcecode:: python
value1 = NSArray.alloc() value2 = NSArray.alloc()
value1 = value1.init() value2 = value2.init()
... (truncated)
Changelog
Sourced from pyobjc-framework-quartz's changelog.
Version 11.1
The major change in this release is aligning behaviour of the core bridge with
clang's documentation for automatic reference counting <https://clang.llvm.org/docs/AutomaticReferenceCounting.html>_ for initializer methods. In particular, PyObjC now correctly models that methods in the "init" family steal a reference to self and return a new reference.In previous version of PyObjC the proxy for
[NSObject alloc]would be marked as 'partially initialized' and would be cleared when the-initmethod returns something else thenself.This has two problems:
Behaviour is incorrect when
+allocreturns a singleton whose-initmethod(s) are factory methods (such asNSArrayin recent versions of macOS)The proxy for Objective-C objects needs to contain mutable state. This in turn requires locking in the implementation to work correctly with free-threading.
This version drops the concept of "uninitialized" values and correctly models how reference counts are handled by
-initmethods.
Update framework bindings for the macOS 15.5 SDK
Added bindings for the
SecurityUIframeworkRestructure the PyObjC website
The theme of the PyObjC websites is now shibuya to give a more modern look and feel to the website.
The actual content is mostly still the same, with some minor restructuring of pages. Restructuring will continue in future updates.
:class:
objc.FSRefnow implements :class:os.PathLike.:issue:
642: Fix concurrency issue when creatingNSArrayinstances usingNSArray.alloc().init....In previous versions the following would fail on recent versions of macOS:
.. sourcecode:: python
value1 = NSArray.alloc() value2 = NSArray.alloc()
... (truncated)
Commits
54423f1Issue #651: Fix build issue in pyobjc-core on macOS 10.122dc6101Update release datecbaf9deRecent free-threaded changes broke 3.13, fix again68f68ecFix issue that prevented running the full test suite4bbcdd0Add error checking to calls to PyObject_IsTrue where needed63f4be6Last bit of the removal ofpkg_resourcesusage.bf1d1f4Add type annotation to some development helpers6c9a01cDrop dependency on pkg_resourcesf09eca2Fix build error with Python 3.109b6493fRe-enable optimized build- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)