Bump pyobjc-framework-fsevents from 10.1 to 10.3.1 in /tools/deps

[dependabot]

Bumps pyobjc-framework-fsevents from 10.1 to 10.3.1.

Release notes

Sourced from pyobjc-framework-fsevents's releases.

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.

• #569: Removed the workaround for a bug in Xcode 15.0

  The workaround is no longer necessary, and caused problems when building with the Command Line Tools development tools from Apple.

• Updated SDK bindings for macOS 14.5

• 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.

• #275: It is now possible to create instances of Objective-C classes by calling the class, e.g. NSObject() instead of NSObject.alloc().init().

  The implementation of __new__ forwards calls to the underlying SomeClass.alloc().init...() pattern. In particular, all public init methods are translated into sets of keyword arguments:

  • Remove init or initWith from the start of the selector name
  • Lowercase the first character of what's left over
  • The strings before colons are acceptable keywords, in that order

  For example, given a selector initWithX:y: the __new__ method will accept x, y as keyword arguments, in that order.

  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.

  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

... (truncated)

Changelog

Sourced from pyobjc-framework-fsevents's changelog.

Version 10.3.1

• :issue: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.

Version 10.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.

• :issue:569: Removed the workaround for a bug in Xcode 15.0

  The workaround is no longer necessary, and caused problems when building with the Command Line Tools development tools from Apple.

• Updated SDK bindings for macOS 14.5

• 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.

• :issue:275: It is now possible to create instances of Objective-C classes by calling the class, e.g. NSObject() instead of NSObject.alloc().init().

  The implementation of __new__ forwards calls to the underlying SomeClass.alloc().init...() pattern. In particular, all public init methods are translated into sets of keyword arguments:

  • Remove init or initWith from the start of the selector name
  • Lowercase the first character of what's left over
  • The strings before colons are acceptable keywords, in that order

  For example, given a selector initWithX:y: the __new__ method will accept x, y as keyword arguments, in that order.

  Framework bindings have been updated with additional metadata to support

... (truncated)

Commits

• 11ec874 Update release information
• b7ce522 Set version to 10.3.1
• d9280a2 Issue #610: Fix regression for code using __init__
• c9b9ac9 fix typo
• d9f5ede Fix link error
• 1b015b7 Release day
• 0c2becb Fix typo
• fe2cb68 Fix off by one error in initializing objc.super
• 3574271 Metadata update run with latest tooling
• 6a799d2 Revert workaround for #569
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[poojadaine]

@dependabot rebase

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.09%. Comparing base (74fc14e) to head (d4588d1).
Report is 36 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4985      +/-   ##
==========================================
+ Coverage   49.24%   52.09%   +2.85%     
==========================================
  Files          94       96       +2     
  Lines       15699    16087     +388     
==========================================
+ Hits         7731     8381     +650     
+ Misses       7968     7706     -262     

Flag	Coverage Δ
functional	42.89% <ø> (+4.81%)	⬆️
integration	2.01% <ø> (-0.06%)	⬇️
unit	40.52% <ø> (+2.94%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[poojadaine]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[poojadaine]

@dependabot rebase

[mr-shekhar]

👍