Bump pyobjc-framework-cocoa from 6.2.2 to 9.0

[dependabot]

Bumps pyobjc-framework-cocoa from 6.2.2 to 9.0.

Release notes

Sourced from pyobjc-framework-cocoa's releases.

v8.5.1

This release contains a small number of bug fixes, most import of which is support for Python 3.11

v8.5

This release continues the work on test coverage in pyobjc-core, resulting in a number of minor bug fixes.

• Added two options to the build_ext command in the setup.py of pyobjc-core:

  • --no-lto: Disable link time optimization

  • --no-warnings-as-errors: Disable -Werror

• For struct bindings in frameworks the "in" operator no longer swallows exceptions raised by the __eq__ method.

• Improved handing of invalid type encodings for struct types.

• Fix crash while handling a struct wrapper with an invalid type encoding.

• Fix handling of empty structs (such as struct foo { }; in :func:objc.repythonify.

• The type for NSObject.pyobjc_instanceMethod and NSObject.pyobjc_classMethods now supports the GC protocol to avoid garbage collection issues when the value for these properties is stored as an attribute (which introduces a reference cycle)

• PyObjC should work with Python 3.11 alpha release, starting at alpha 6. Earlier alpha's are not supported due to reverting a workaround for a bug that was fixed in alpha 6.

• NSObject.alloc = 42 now fails. It was already impossible to replace a selector by something else through instances (NSObject.new().description = 42 raises).

• Added :data:objc.ObjCPointer.typestr with the same value as :data:objc.ObjCPonter.type. The latter is now deprecated and will be removed in PyObjC 9.

• Better error messages when a class implementing a protocol inherits a method of the wrong kind ("class" vs. "instance").

• The value of __slots__ in a class definition is now kept in the created class (previous versions always set the attribute to an empty tuple).

... (truncated)

Changelog

Sourced from pyobjc-framework-cocoa's changelog.

Version 9.0

• Support for macOS 13 (Xcode 14 beta 4)

• Updated framework bindings for macOS 13

  The list below lists the frameworks that have API changes that affect the framework bindings.

• Added bindings for the following frameworks (all new in macOS 13):

  • AVRouting
  • BackgroundAssets
  • ExtensionKit
  • HealthKit
  • MetalFX
  • SafetyKit
  • SharedWithYou
  • SharedWithYouCore
  • ThreadNetwork

• The definition of a number of basic structs has moved in the SDK for macOS 13 and PyObjC conforms to this change on all platforms.

  In particular:

  • CGPoint, CGSize, CGVector, CGRect, CGAffineTransform and CGAffineTransformComponents are now defined in the CoreFoundation module.
  • NSPoint, NSSize and NSRect are now aliases for the corresponding CG* types (instead of the other way around in previous versions of PyObjC).

  Both changes should require no changes to scripts, unless code relies on the particular __name__ of a type.

• The extension API ("pyobjc-api.h") now has nullability annotations, which may lead to compilation errors or warnings when compiling 3th-party extensions using this API.

• The extension API ("pyobjc-api.h") has a changed interface for creating method IMPs, because of this extensions for older versions of PyObjC cannot be used with PyObjC 9.

• #416: PyObjC 9.0 requires Python 3.7 or later

• #384: Remove support for BridgeSupport files

  The bridge itself hasn't used these files for a long time, and system bridgesupport files are basically unusable.

• #415: Remove objc._setClassExtender

... (truncated)

Commits

• 595adfb Update changelog entry for Nuitka support
• bb0d803 Minor update to documentation index for the 9.0 release.
• 69ed506 Prepare for the 9.0 release
• dc8d474 Fix some test failures on Python 3.8
• c99517f Fix compile error
• b0c5546 Port fix from 8.x branch
• e3771a7 Merge branch 'master' of github.com:ronaldoussoren/pyobjc
• 5e08544 Fix a number of test results, getting there...
• 56e1895 Avoid using a large static buffer in super-call.m
• a4419fd Clear error that when comparing signatures
• 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 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)

[dependabot]

Superseded by #48.