Ronald Oussoren

I’ve tagged and uploaded PyObjC 10.3 to PyPI. This is a fairly substantial update feature wise: It is now possible to instantiate most classes using the regular Python convention instead of Objective-C’s explicit two-step construction.

That is, NSObject() is now a valid alternative to NSObject.alloc().init().

The basic idea is that all init selectors are translated into sets of acceptable keywords for instantation, see PyObjC’s docmentation for more details.

This is a first step towards adding more Pythonic method name aliases to PyObjC

PyObjC 9.2 is uploading to PyPI. This contains a number of bugfixes, as well as support for Python 3.12 (tested with beta 1).

PyObjC will now also warn about code that uses argumentless super() when super doesn’t resolve to PyObjC’s objc.super. Using builtin.super for resolving superclass attributes for Objective-C classes can result in subtle errors. Using objc.super instead fixes those errors, and is safe to use with regular python classes as well.

The correct code pattern is:

from Foundation import NSObject
from objc import super  # Use ``objc.super`` instead of ``builtin.super``


class MyObject(NSObject):
    def init(self):
         self = super().init()
         if self is None:
             return None

         ...
         return self

PyObjC 9.1 is one of the rare times that I’m publishing explicit beta releases. PyObjC 9.1b1 is available on PyPI (pip install pyobjc-9.1b1).

This release contains the usual SDK updates (macOS 13.3) and minor bugfixes, but more importantly it contains some major changes to pyobjc-core. Because of this I kindly request that you test this beta release and let me know about any problems.

First of all the code that transforms class attributes, and in particular translates Python functions to objc.selector objects, was rewritten from C to Python. This change should be transparant for users, other than some error cases and intentation changes:

1. The new code is smarter about recognizing if a method is intended to be used as an Objetive-C selector and will not translate multi-word PEP8 compatable names (e.g. “my_,method”). This reduces the need to use the python_selector decorator.

2. Coroutings (async methods, iterators) are no longer translated to a selector

3. The new code will translate all callables, which may lead to needing to use the python_method decorator in some cases (e.g. when using a builtin function as a class attribute)

4. It is now possible to use varargs in a selector method when the implied number or arguments can be represented.

Furthermore the python_method and informal_protocol classes are now implemented in Python instead of Objective-C. Those should have no user-visible changes in behaviour.

Lastly a number of classes are now created using PyType_FromSpec instead of using static PyTypeObject definitions. That results in minor change in behaviour when using Python 3.9 or earlier: In those versions it is not possible to make these classes immutable. Don’t rely on this behaviour.

As always the full changelog can be seen at https://pyobjc.readthedocs.io/en/latest/changelog.html.

I’ve (finally) tagged the PyObjC 9.0 release and uploaded it to PyPI.

As usual with a major release this release includes support for the APIs introduced in the latest macOS release, macOS 13 (Ventura).

Other noteworthy changes are:

• Dropped support for Python 3.6 as that Python version is no longer supported by the CPython project

• Added support for APIs using SIMD/vector types in C (such as the vector_float3 type), with relevant type definitions in the new objc.simd module.

• This release should be compatible with Nuitka (this requires Nuitka 1.1.6 or later)

The full list of changes is in the changelog.