Bump pyobjc-core from 6.2.2 to 8.3

[dependabot]

Bumps pyobjc-core from 6.2.2 to 8.3.

Release notes

Sourced from pyobjc-core's releases.

v8.3

This release contains a lot of small fixes dueo to the continued improvement of test coverage for the C code in pyobjc-core.

• Backward incompatible change:

  -[OC_PythonDictionary setObject:value forKey:[NSNull null]] now sets key :data:None in the Python dictionary instead of NSNull.null().

  This is for consistency with -[OC_PythonDictionary objectForKey:] and other collection classes. Getting and setting key [NSNull null] now actually works.

• Backward incompatible change:

  -[OC_PythonDictionary removeObjectForKey:] now raises NSInvalidArgumentException instead of Python's KeyError for missing keys. This matches the documented behaviour of NSDictionary.

• Backward incompatible change:

  -[Protocol descriptionForClassMethod:] now only accepts selector names (such as b"description") as its argument, not instances of :class:objc.selector. This matches the behaviour of other methods with an argument of the C type SEL.

• :func"objc.namedSelector and :func:objc.typedSelector now also work when the decorated function is a :func:classmethod.

• Fix build problem on macOS 10.14 or earlier

• The Objective-C proxy for a python :class:int is now always OC_PythonNumber, in previous versions instances were proxied as NSNumber when the value was in the range of an unsigned long long that's outside of the range of a (signed) long long (that is, a value between 2**63 and 2**64).

• Two NSString* values in Objective-C are now proxied to the same :class:objc.pyobjc_unicode instance when the two pointers are equal in Objective-C.

  That is, given NSString* value1 and NSString* value2 value1 == value2 in Objective-C can be replaced by value1 is value2 in Python. In older versions of PyObjC this invariant was not maintained, requiring more involved code to check if two strings represent the same object.

  This invariant was already maintained for other instances of other Objective-C classes.

... (truncated)

Changelog

Sourced from pyobjc-core's changelog.

Version 8.3

This release contains a lot of small fixes dueo to the continued improvement of test coverage for the C code in pyobjc-core.

• Backward incompatible change:

  -[OC_PythonDictionary setObject:value forKey:[NSNull null]] now sets key :data:None in the Python dictionary instead of NSNull.null().

  This is for consistency with -[OC_PythonDictionary objectForKey:] and other collection classes. Getting and setting key [NSNull null] now actually works.

• Backward incompatible change:

  -[OC_PythonDictionary removeObjectForKey:] now raises NSInvalidArgumentException instead of Python's KeyError for missing keys. This matches the documented behaviour of NSDictionary.

• Backward incompatible change:

  -[Protocol descriptionForClassMethod:] now only accepts selector names (such as b"description") as its argument, not instances of :class:objc.selector. This matches the behaviour of other methods with an argument of the C type SEL.

• :func"objc.namedSelector and :func:objc.typedSelector now also work when the decorated function is a :func:classmethod.

• Fix build problem on macOS 10.14 or earlier

• The Objective-C proxy for a python :class:int is now always OC_PythonNumber, in previous versions instances were proxied as NSNumber when the value was in the range of an unsigned long long that's outside of the range of a (signed) long long (that is, a value between 2**63 and 2**64).

• Two NSString* values in Objective-C are now proxied to the same :class:objc.pyobjc_unicode instance when the two pointers are equal in Objective-C.

  That is, given NSString* value1 and NSString* value2 value1 == value2 in Objective-C can be replaced by value1 is value2 in Python. In older versions of PyObjC this invariant was not maintained, requiring more involved code to check if two strings represent the same object.

  This invariant was already maintained for other instances of other

... (truncated)

Commits

• 373e2d7 Merge branch 'master' of github.com:ronaldoussoren/pyobjc
• 79a9468 Update version to 8.3
• 1210bf8 Update stale headers
• 41d85bd Fix -Wunused-but-set-variable warnings
• 59a6ca9 Mention that appscript is deprecated
• a29883f Fix broken link
• 724375b Add better tests for C callables returning a null terminated C array #393
• 1bf56fc Switch to using @​throw for raising Objective-C exceptions
• f96b0ab Futher improvements of test coverage #393
• b6322b4 Futher improvements of test coveage #393
• 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 #67.